Abstract: Flight planning and/or optimizing flight plans can be performed using ground-based systems with little or no instrumented data, providing efficient communications between aircraft and ground-based systems. Estimates of airspeeds (i.e., derived airspeed) can be derived from transponder telemetry, which is optionally collected independently of flight planning. Alternative (adjusted or revised or modified) flight plans can be generated based on derived airspeed, weather, traffic, etc., and/or performance data specific to an individual aircraft. Aircraft performance models can be updated (e.g., fuel consumption) based on monitoring an aircraft over time. Winds aloft data can be updated based on monitoring of one or more aircraft. Data can be selectively identified and uplinked to aircraft based on certain criteria (e.g., data relevant to geographic areas and altitudes proximate flight path as indicated by flight plan).

Abstract: Systems, apparatuses, and methods for acquiring information regarding weather conditions along a flightpath from other aircraft and incorporating that information into a flight path optimization and planning system. The system and methods may acquire substantially real-time information from pilots or other crew who have encountered a weather system or event (e.g., a wind direction or speed measurement, an observation of a storm or lightning, an observation of a difficulty in controlling an aircraft, unexpected excessive turbulence, etc.) and share that information with other airborne pilots or crew, either directly or using a ground-based server. The server may receive and process the acquired information and determine which aircraft may be likely to encounter or be impacted by a weather system or event for which it has received additional weather-related data and information.

Abstract: In connection with processing asynchronous streams of aircraft telemetry data, data processing logic is developed to run on multiple aircraft, even if different avionics equipment are installed on the aircraft. An electronic inventory system tracks data available on affected aircraft. A set of “global” data elements applicable to aircraft in a fleet is defined and is tracked in the electronic inventory system, with relationship to the underlying native data elements and specific aircraft. The global units are derived as appropriate, for each specific aircraft avionics environment. An interface enables definition of data processing logic that is integrated with the electronic inventory system and ensures the general validity of the defined logic. The data processing logic is deployed to one or more aircraft in a function integrated with the electronic inventory system, to ensure the validity of the data processing logic for each aircraft specified as a deployment target.