US20070129855A1 - Device and method of automated construction of emergency flight path for aircraft - Google Patents
Device and method of automated construction of emergency flight path for aircraft Download PDFInfo
- Publication number
- US20070129855A1 US20070129855A1 US11/567,948 US56794806A US2007129855A1 US 20070129855 A1 US20070129855 A1 US 20070129855A1 US 56794806 A US56794806 A US 56794806A US 2007129855 A1 US2007129855 A1 US 2007129855A1
- Authority
- US
- United States
- Prior art keywords
- aircraft
- procedures
- flight plan
- navigation aid
- approach
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/0047—Navigation or guidance aids for a single aircraft
- G08G5/0056—Navigation or guidance aids for a single aircraft in an emergency situation, e.g. hijacking
-
- G—PHYSICS
- G08—SIGNALLING
- G08G—TRAFFIC CONTROL SYSTEMS
- G08G5/00—Traffic control systems for aircraft, e.g. air-traffic control [ATC]
- G08G5/003—Flight plan management
- G08G5/0039—Modification of a flight plan
Definitions
- the present invention applies to flight management systems for aircraft with or without a pilot on board.
- Such systems provide pilot assistance functions for determining the route to be followed by the aircraft to home in on its destination from its departure point taking into account the regulatory and operational constraints to be observed.
- an aircraft navigation aid device including means for preparing a flight plan and path of said aircraft including a navigation database, characterized in that it further includes means of storage in the form of a computer database of procedures to be used in predefined emergency situations and means of computer processing enabling the flight plan and path in progress to be modified in accordance with the procedures applicable to each emergency situation and optimally for a preference function chosen from a combination of navigation criteria.
- FIG. 1 depicts the functional architecture of a flight management system incorporating the invention
- FIG. 2 shows the communication links of a drone
- FIG. 3 displays the processing flow chart in a mode of embodiment of the invention in the case where the aircraft is ‘en route’;
- FIG. 4 shows a flight plan example in the case where the aircraft is ‘en route’
- FIG. 5 displays the processing flow chart in a mode of embodiment of the invention in the case where the aircraft is on takeoff;
- FIG. 6 shows a flight plan example in the case where the aircraft is on takeoff
- FIG. 7 displays the processing flow chart in a mode of embodiment of the invention in the case where the aircraft is on approach;
- FIG. 8 shows a flight plan example in the case where the aircraft is on approach
- FIG. 1 shows the functional architecture of an FMS 10 .
- Such systems are covered by the ARINC 702 standard (Advanced Flight Management Computer System, December 1996). They normally provide all or part of the functions of: navigation LOCNAV, 170 , for optimum localization of the aircraft according to the means of geo-localization (GPS, GALILEO, VHF radio beacons, inertial units); flight plan FPLN, 110 —Navigation database NAVDB, BDN, 130 , for constructing geographical routes and procedures from data included in the databases (points, beacons, intercept or altitude legs, etc.); lateral flight path TRAJ, 120 : for constructing a continuous flight path from flight plan points observing aircraft performances and confinement constraints (RNP); predictions PRED, 140 : for constructing an optimized vertical profile on the lateral flight path; guidance, for guiding the aircraft on its 3D flight path in the lateral and vertical planes, while optimizing speed; digital data link DATALINK, 180 for communicating with control centers and other aircraft.
- GPS
- FIG. 1 shows an FMS with all the functions above. It further comprises the additional functions necessary for implementing the invention. This means the computer database of procedures ESPDB, BDP, 150 and the computer processing module for implementing the invention ESPU, 160 .
- the computer database of procedures may advantageously be of the object type. It stores the data necessary for carrying out procedures. This information is derived from paper maps and compressed.
- the database will comprise without limitation: geographical data on TMAs (center of the cone, width, height); data on MSAs; legs for modeling takeoff procedures; data for modeling landing attempts (number of “Missed approach” type procedures to be performed before leaving the TMA); data for the ‘En Route’ part, such as the ICAO data (hold time at constant level), explained in section 1.1, the regional/state data amending the ICAO data (in particular, hold time, holding time on HOLD), the ICAO data on the arrivals to be effected (section 1.1), the data on the arrivals to follow on the airfields when they differ from ICAO data; validity dates which may be identical to those of the navigation database (updated every 28 days, or more often, via “patch”, if procedures change in the meantime).
- the computer processing module for implementing the invention consists of a software module capable of being executed on a standard FMS computer such as the THALES AVIONICS NEW FMS, currently flying on the whole Airbus product range (redundant computer). . . .
- the source program will advantageously be programmed in ADA or C complying with the standards to be observed for the code to be able to be certified.
- the process coded by the program ensures the selection of procedures, examples of which have been given above, in the computer database of procedures, prepares an optimized flight path in case of emergency (engine failure, loss of communications, etc.), based on the emergency procedures database, the airspaces crossed, the airplane's performances, traffic, weather, relief, ensures the progress of this flight path and the sending of the flight path to the ground, if air-to-ground communication via Datalink is possible.
- FIG. 2 shows the communication links of a drone 30 .
- the loss of the communication link between control and the drone poses a problem since the pilot on the ground no longer receives control instructions.
- the loss of the communication link between the drone and the ground station means that the pilot on the ground is no longer aware of the “voice” instructions from the control centre.
- the pilot will or will not intervene in the execution of the procedures.
- the proposed device and system enable fully automatic execution, on condition that all the necessary FMS functions are on board.
- the choice of optimum architecture must be made according to prescribed operational use conditions, taking into account the constraints of weight, space requirement and cost which lead to a transfer of computing power towards the ground station.
- the process may further offer a number of strategies to the crew, enabling them to choose between several flight paths, observing all the regulations, but optimizing different criteria.
- the preference function also applicable in the case of unmanned aircraft, will most often favor enhanced safety in terms of minimum separation from other aircraft and relief elements, but it is easy to construct a preference function which will be capable of being programmed according to the operational context. Most often, a second rank optimum obtained by parts will be sufficient. However, if the operational context calls for it, nothing prevents seeking a complete solution for the preference function optimum, on condition that the necessary computing power is available.
- the FMS may extend cruising if necessary to keep a 20 min segment in front of the aircraft at constant level. It erases any STEPS that may be present in front of the aircraft in the 20 min interval.
- the FMS uses the “Constant Mach Segment” function on the points in front of the aircraft, at least over the predicted 20 mins, for flying at constant speed.
- MORA Minimum Off Route Altitude
- the FMS computes and inserts a “STEP CLIMB” in front of the aircraft to be 2000 feet above the highest MORA in the 20 min interval. Laterally, the FMS follows the active flight plan, but modifying the transitions (turns) between portions of the flight plan to remain compatible with the airplane speed. After said 20 mins, the FMS returns to the preprogrammed vertical flight plan, as well as to the preprogrammed speed by canceling the STEP and CMS that may have been entered in the first 20 min phase.
- the FMS vertically controls the aircraft to follow the end-of-cruise and descent flight plan up to the approach point required by the procedure, namely the recommended beacon (if ICAO) or another point such as the IAF in France.
- the FMS inserts a holding pattern in its flight plan, adopting the assumptions explained below.
- the FMS inserts this HOLD; otherwise, it utilizes the HOLD function, with the following parameter settings:
- the FMS uses the “IMMEDIATE EXIT” function to exit the holding pattern when it predicts an arrival time compatible with the initially planned time, and adjusts the initiation of the function to ensure a landing within the 30 mins around the planned time.
- the other systems may transmit signals such as “TRANSMITTING BLIND”, code 7700, according to the type of failure.
- Step 1 ( 410 , 420 , 430 ): on detecting the failure: FMS:
- the FMS checks to see whether there is a “hold time” in the current geographical area in the BDP. If so, it applies this time, if not, the ICAO value of 20 mins is used. In the example, a time of 7 mins is found and will be applied. During this period, the FMS freezes the speed of the aircraft at the current value and the level at the current level. The FMS calculates a rejoin onto the active flight plan by creating an orthogonal projection of the airplane onto it to identify the rejoin segment and making a turn whose angle optimizes the clearance with other aircraft. For this, one possibility is to test for a rejoin every 5°, between an intercept at 45° and an intercept at 90°; for each rejoin value.
- the FMS looks to see whether the other surrounding aircraft will cut across the rejoin track with a vertical clearance of less than 500 feet; for aircraft that cut across the rejoin segment, the FMS extrapolates the position of these aircraft from the speed and heading data obtained by interrogating the MODE S transponder of the aircraft in question (TCAS or ADS-B function); the FMS then compares the passage times of the aircraft that cut across the track with its passage times at the same point.
- TCAS MODE S transponder of the aircraft in question
- ADS-B function ADS-B function
- rejoin 310 which is the optimum solution, is that which makes an angle of 45° with the flight path.
- the FMS checks the value of the MORAs from the BDN and where necessary adjusts the flight level, then it checks the absence of conflict in the vertical plane with other aircraft, at the level in question. If a conflict is detected, the algorithm loops back until it finds a solution.
- Step 2 440 : Return to the managed vertical and speed after “hold time”.
- One possible calculation algorithm is as follows: If the FMS predicts a rejoin onto the flight plan over a period greater than “hold time”, it remains at constant speed and level until the rejoin, then goes back to “managed Speed and Vertical”, that is, at the optimum level and speed calculated by the FMS; if the FMS predicts a rejoin before elapse of “hold time”, it continues on the flight plan until reaching the “hold time”, then goes back into “managed Speed and Vertical”; on arriving at the end-of-cruise point (T/D), the FMS reassigns the descent level to that of the approach point originating from the BDP and engages the descent.
- Step 3 450 Insertion of a HOLD at the approach point, and constraint at this point to remain above the relief (raised by the MSA).
- the FMS inserts a HOLD at the approach point of the BDP in the following way: If a HOLD already exists at the approach point, the FMS uses this HOLD; otherwise, if a HOLD is coded in BDN at this point, the FMS inserts this HOLD; otherwise, the FMS inserts a HOLD with a right turn, length of right leg 1 min, ICAO speed. At the point of entry and exit of the HOLD, the FMS inserts an altitude constraint equal to the MSA retrieved from the BDP if it exists. Otherwise, the FMS inserts a constraint equal to the value of the ILS GLIDE beam intercept if it exists, and, if not, constructs a default approach and inserts a constraint equal to the deceleration level on this approach.
- Step 4, 460 Optimization of the moment of exit from HOLD to land closest to the initially estimated time, and at the maximum in the next 30 mins.
- the FMS flies the HOLD until the predicted landing time matches the initially estimated time; otherwise, the FMS uses the 30 min slot until a landing weight is attained below the threshold authorized on the runway; in any case, at the end of 30 mins deviation from the estimated time, the FMS exits the HOLD and continues the approach.
- Step 5 Determination of the landing procedure
- a possible algorithm is the following: If a procedure is coded before detection of the failure, the FMS follows this procedure; if no procedure is coded, the FMS searches for the approach procedure that maximizes precision, taking its on-board means into account. It will use in order: ILS, MLS, GLS, FLS, GPS, VOR/DME; if no approach is possible with the above means, the FMS produces a “Runway by itself” approach by stringing a segment in the runway track, with ⁇ 3° of slope over 5 NM, on the opposite side to the wind.
- the FMS detects a radionavigation means failure for carrying out the approach in question, it changes over to the “emergency landing procedure” algorithm explained in the corresponding example of embodiment.
- the FMS controls the extension of slats, flaps and landing gear on the approach, as the pilot would do, when it reaches the associated characteristic speeds.
- This very common type of procedure may be expressed in the following way in a flight management system: Aircraft in MANAGE (fully automatic control); insertion of an “AT OR BELOW” altitude constraint at the SID points, equal to the last level assigned by control, where applicable raised by the MSA (avoidance of an obstacle); holding at this level until the geographical limits of the TMA, to be coded into a database; return to the FMS active flight plan, which will automatically switch over to climbing up to cruise level entered on the ground; application of the “En Route” procedure described above.
- This “On Takeoff” mode of embodiment is illustrated by the example in FIG. 6 .
- the aircraft is down below and has just taken off.
- the active flight plan passes through the points WP 1 . . . WP 5 .
- Points WP 1 . . . WP 4 are the points of the SID, and point WP 5 is the first point of the “EN ROUTE” part.
- the “comm failure” flight plan stored in BDP passes through WP 1 , WP 6 , WP 7 .
- the hexagon represents the TMA.
- the processing flow chart of this mode of embodiment for this example is that in FIG. 5 .
- the FMS By calling up the BDP, the FMS loads the “Emergency Situation” flight plan applicable to the emergency situation detected in the current phase.
- the FMS loads the coordinates of the characteristic points of the TMA and determines the first point outside of the TMA on the active flight plan (here WP 5 ).
- the FMS strings the “Emergency Situation” flight plan onto this first point, minimizing the distance and following the outlines of the TMA; the following is a possible algorithm: A margin of X NM (5 NM for example) is determined with respect to the polyhedron, at the level of the polyhedron break points, a point is created on the bisector segment, 5 NM from the outline; then these points are connected up to WP 5 ; this calculation is made starting from both the left and the right, at the end of the “Emergency Situation” flight plan and the one with the least distance is kept.
- a margin of X NM (5 NM for example) is determined with respect to the polyhedron, at the level of the polyhedron break points, a point is created on the bisector segment, 5 NM from the outline; then these points are connected up to WP 5 ; this calculation is made starting from both the left and the right, at the end of the “Emergency Situation” flight plan and the one with the least distance is kept.
- “AT OR ABOVE” altitude constraints are inserted on the points of this flight plan at the value of the MSA of the sector originating from the BDN on the “Emergency Situation” starting procedure points.
- the FMS assigns a cruise level equal to the last level obtained from control. No constraint is inserted on the last starting procedure point (here WP 7 ), just as on the next EN ROUTE points (here WP 5 ), so that the climb profile is calculated to climb to the cruise level, i.e. to the last level assigned by control.
- the FMS guides along this flight plan then passes onto the “En Route Emergency Situation” part.
- the procedure is: “In the case where the pilot has no knowledge of the runway in use, employ the procedure for RWY03 (A circle before landing may be necessary if the wind observed by the pilot indicates that RWY21 is in use). In the event of a missed approach, employ the corresponding published procedure and begin a second approach. If the second approach fails, follow the applicable corresponding procedure then leave the TMA at 3000 feet and try to attain VMC”.
- VMC visual conditions procedure
- the FMS retrieves the “Emergency Situation” flight plan from the BDP (here continuation of the Missed Approach then attempt at second approach. The FMS then switches over to step 5 of the “En Route” part to determine the best radionavigation means for landing on this runway.
- the LEAVING TMA procedure is not employed since VMC conditions are inapplicable. The drone will continue its approaches until it succeeds in one, even if it must lead to damage to the craft.
- the process may follow the procedure to the end.
- the FMS will therefore offer to follow the same routing as above and, in the event of a 2 nd landing failure, will retrieve the TMA polyhedron from the BDP, string a straight line to the last Missed Approach point in the axis of this last segment up to the TMA limit, possibly constraining the created points in altitude (here 3000 feet).
- the last emergency procedure will normally be the intervention of fighter planes which will guide the aircraft in its landing.
- the procedure is: “In the case where the pilot has no knowledge of the runway in use, employ the procedure for RWY03 (A circle before landing may be necessary if the wind observed by the pilot indicates that RWY21 is in use). In the event of a missed approach, employ the corresponding published procedure and begin a second approach. If the second approach fails, follow the applicable corresponding procedure then leave the TMA at 3000 feet and try to attain VMC”.
- VMC visual conditions procedure
Abstract
Description
- The present invention applies to flight management systems for aircraft with or without a pilot on board. Such systems provide pilot assistance functions for determining the route to be followed by the aircraft to home in on its destination from its departure point taking into account the regulatory and operational constraints to be observed.
- These constraints include the procedures to be employed in given emergencies as prescribed by international organizations, state and airport authorities. In particular, such cases include aircraft hijacking, medical emergencies, malfunctions affecting the aircraft's flight qualities (engine, pressurization, etc.), communication failures, making ground/air or air/air dialogue, and accordingly control of the aircraft in question impossible. According to Eurocontrol, the body responsible for controlling European airspace, such communication failures (Prolonged Loss of Communication or PLOC) involved over 1000 flights between 1999 and 2005. These failures increase the risk of collision and have a significant cost since they must be taken into account in air traffic control design to enable traffic reorganization when they occur. In the extreme, these failures mean forcing the airplane to the ground by fighter planes.
- The procedures to be employed in these emergencies depend on the location of the aircraft, which determines the applicable regulations. They are therefore voluminous and complex. Furthermore, they do not prescribe any single solution that can be directly integrated into a flight management system since a choice must be made from an infinite number of options. This explains why in the present state of the art there is no solution for automatically or semi-automatically taking these procedures into account in a flight management system. This is a significant drawback for aircraft with a pilot on board, since there is a heightened risk of misapplication of complex procedures by the crew and potential breaches of security are greater. It is a completely unacceptable drawback for military aircraft whose pilot is not on board, known as drones. These may be authorized to fly in non-segregated airspace, i.e. shared by civil aircraft, only if they are able to apply the same regulations and procedures, particularly in the event of an emergency situation. But currently this cannot be ensured for a drone, particularly in the event of a communication failure. In fact, if it is the control link that is interrupted, the extreme solution of instructions visually communicated by fighter planes is not applicable; if it is the link between the drone and its pilot that is interrupted, the latter cannot give any instruction to the aircraft.
- The solution to the problem consisting in automatically or semi-automatically taking account of procedures to be applied in emergency situations in a flight management system is therefore particularly critical.
- To this end, the present invention provides an aircraft navigation aid device including means for preparing a flight plan and path of said aircraft including a navigation database, characterized in that it further includes means of storage in the form of a computer database of procedures to be used in predefined emergency situations and means of computer processing enabling the flight plan and path in progress to be modified in accordance with the procedures applicable to each emergency situation and optimally for a preference function chosen from a combination of navigation criteria.
- It also provides a method of using said device.
- It offers the advantage of great versatility, since it is adapted to different emergency situations described above, to different flight configurations (‘en route’, on takeoff or on approach), to aircraft whose pilot is on board or not and it can also be used in pilot assistance automatic or semi-automatic mode.
- The invention will be better understood and its different features and advantages will emerge from the disclosure which follows several examples of embodiment and its accompanying figures, of which:
-
FIG. 1 depicts the functional architecture of a flight management system incorporating the invention; -
FIG. 2 shows the communication links of a drone; -
FIG. 3 displays the processing flow chart in a mode of embodiment of the invention in the case where the aircraft is ‘en route’; -
FIG. 4 shows a flight plan example in the case where the aircraft is ‘en route’; -
FIG. 5 displays the processing flow chart in a mode of embodiment of the invention in the case where the aircraft is on takeoff; -
FIG. 6 shows a flight plan example in the case where the aircraft is on takeoff; -
FIG. 7 displays the processing flow chart in a mode of embodiment of the invention in the case where the aircraft is on approach; -
FIG. 8 shows a flight plan example in the case where the aircraft is on approach; - In the disclosure and the figures, the initials, acronyms and abbreviations have their meanings in French and English shown in the table below. We show the meaning in English since this is what is used in everyday language by persons skilled in the art, even in France.
Acronym Meaning in English Meaning in French ADS-B Automatic Dependent Surveillance - Surveillance automatique de Broadcast dépendance - Broadcast AOC Airline Operations Center Centre d'opérations de la compagnie aérienne AP Auto pilot Pilote automatique AP AP interface Interface avec le pilote INTERFACE automatique ARINC Aeronautical Radio Inc Organisme de normalisation aéronautique APP Approach Phase d'approche ATC Air Trafic Control Contrôle du trafic aérien BDN/NAVDB Navigation database Base de données de navigation BDP/USDB Urgency [Emergency] Situation Base de données informatique Procedures database des procédures d'urgence CMS Constant Mach Segment Segment de vol à mach constant CRZ FL Cruise Flight Level Altitude de croisière du vol DATALINK Digital Communication link Liaison de communication numérique DES Descent Phase de descente DME Distance Measurement Equipment Equipement de mesure de distance DO-236B RTCA group document describing among other things the speeds required for certain procedures. ESDET Emergency Situation Detection Détection de situation d'urgence ESPU Emergency Situation Processing Unit Unité de traitement des situations d'urgence ETOPS Extended range with Twin engine Opérations d'avion long courier aircraft Operations bi-moteur FLS FMS Landing system Système d'atterrissage FMS FMS Flight Management system Système de gestion de vol FPLN Flight Plan Plan de vol GALILEO European GPS [satellite] constellation GLIDE Radio beam in the vertical plane for precision guidance in ILS approach GLS GPS Landing system Système d'approche utilisant le GPS GPS Global Positioning system Système de positionnement global HOLD Holding Pattern Boucle d'attente en approche, souvent appelée hippodrome IAF Initial Approach Fix Point fixe d'approche initiale ILS Instrument Landing system Système d'atterrissage aux instruments IMC Instrument Meteorological Conditions Conditions météo pour le vol aux instruments INR Inertial sensors Capteurs d'inertie LOCNAV Localization means for navigation Moyens de localisation pour la navigation MLS Microwave Landing system Système d'atterrissage micro- ondes MMI Man Machine Interface Interface homme machine MORA Minimum Off Route Altitude Altitude minimale hors route MSA Minimum Sector Altitude Altitude minimale du secteur NAVDB/BDN Navigation database Base de données de navigation NDB Non-Directional Beacon Balise sol permettant la localisation par relèvement NM Nautical Mile Mille nautique OACI Organisation de I'Aviation Civile International Civil Aviation Internationale Organization (ICAO) PANS Procedure for Air Navigation services Procédure pour les services de (ICAO documents) navigation aérienne (documents OCI) PRED Prediction Prédiction RNP Required Navigation Performance Performance prescrite de navigation SENS Sensors Capteurs SID Standard Instrument Departure Décollage standard aux instruments SSR Secondary surveillance Radar Radar secondaire de surveillance STAR Standard Terminal Arrival Route Route terminale standard STEP Cruise level change Changement de niveau en croisière TCDS Terrain Collision Avoidance System Système anti-collision terrain T/D Top Of Descent Point de fin de la croisière TMA Terminal Area Zone terminale TRAJ Trajectory [Flight Path] Trajectoire UAV Unmanned Aerial Vehicle (Drone) Avion non piloté ESPDB/BDP Emergency Situation Procedures Base de données informatique database des procédures d'urgence VHF Very High Frequency Trés haute fréquence VMC Visual Meteorological conditions Conditions météo pour le vol à vue. VOR VHF Omni Range Balise VHF omni directionnelle -
FIG. 1 shows the functional architecture of an FMS 10. Such systems are covered by the ARINC 702 standard (Advanced Flight Management Computer System, December 1996). They normally provide all or part of the functions of: navigation LOCNAV, 170, for optimum localization of the aircraft according to the means of geo-localization (GPS, GALILEO, VHF radio beacons, inertial units); flight plan FPLN, 110—Navigation database NAVDB, BDN, 130, for constructing geographical routes and procedures from data included in the databases (points, beacons, intercept or altitude legs, etc.); lateral flight path TRAJ, 120: for constructing a continuous flight path from flight plan points observing aircraft performances and confinement constraints (RNP); predictions PRED, 140: for constructing an optimized vertical profile on the lateral flight path; guidance, for guiding the aircraft on its 3D flight path in the lateral and vertical planes, while optimizing speed; digital data link DATALINK, 180 for communicating with control centers and other aircraft. - For implementing the invention, only the flight plan and path preparation functions are necessary. However,
FIG. 1 shows an FMS with all the functions above. It further comprises the additional functions necessary for implementing the invention. This means the computer database of procedures ESPDB, BDP, 150 and the computer processing module for implementing the invention ESPU, 160. - The computer database of procedures may advantageously be of the object type. It stores the data necessary for carrying out procedures. This information is derived from paper maps and compressed. The database will comprise without limitation: geographical data on TMAs (center of the cone, width, height); data on MSAs; legs for modeling takeoff procedures; data for modeling landing attempts (number of “Missed approach” type procedures to be performed before leaving the TMA); data for the ‘En Route’ part, such as the ICAO data (hold time at constant level), explained in section 1.1, the regional/state data amending the ICAO data (in particular, hold time, holding time on HOLD), the ICAO data on the arrivals to be effected (section 1.1), the data on the arrivals to follow on the airfields when they differ from ICAO data; validity dates which may be identical to those of the navigation database (updated every 28 days, or more often, via “patch”, if procedures change in the meantime). These procedures are codified in the following documents drawn up on the basis of ICAO recommendations: Rules of the Air (
Annex 2 of the Chicago Convention); Aeronautical Telecommunications (Annex 10); Procedures—Rules of the Air and Services, PANS-RAC Doc 4444; Procedures—Operations, PANS-OPS (Doc 8168). They may also be drawn up based on state amendments adapting these recommendations to particular situations. - These emergency procedures are currently described in international or state paper documents and collected together by the database suppliers. Some of these procedures (
Annex 10, vol. II) are to be followed in the event of communication failure to try to establish emergency communications, to notify air traffic control services and other aircraft in the area of the situation and to request the assistance of these aircraft, for example by relaying messages from other aircraft. These procedures have little interaction with the flight plan and path preparation functions. The purpose of other procedures is to cleanly “pull out” the airplane from traffic so as to ensure separations between aircraft, as well as its safety vis-á-vis the relief. - The procedures to be employed will differ according to whether the aircraft is ‘En Route’, on Takeoff or on Approach.
- In the event of communication failure between ground and air, as well as between aircraft (in the case of the Drone, one entails the other), in IMC, ‘En Route’,
Annex 2 of the Chicago Convention, paragraph 3.6.5.2.2 prescribes: -
- Maintaining the current speed and level, if necessary raised to the minimum altitude for 20 mins;
- Adjusting the level and speed in accordance with the active flight plan
- Flying up to the beacon recommended for the destination airport
- Holding pattern on the beacon in question, in descent, and keeping in the holding stack until the specified approach time or the time enabling landing at the estimated time (RTA) of the active flight plan.
- Instrument approach to the airport, using the beacon
- Landing within a maximum of 30 mins after the estimated time of arrival.
- In the event of on-board receiver failure, VHF transmission of the message “TRANSMITTING BLIND DUE TO RECEIVER FAILURE” (
Annex 10, vol. II) - In the event of transmission failure to an ATC center, VHF transmission “TRANSMITTING BLIND” (
Annex 10, vol. II) - Selection of the appropriate SSR on the transponder. (
Annex 10, vol. II)
- These procedures may be amended and modified by local regulations. In France, for example:
-
- ‘En Route’, the IAF is used instead of the beacon of the ICAO proc.
- Regarding terminal procedures of the STAR, APP, SID type, local regulations may lay down specific procedures. In France, for example, in the event that it is impossible to land for any reason, leaving the TMA within 30 mins according to the “LEAVING PROCEDURE” (Takeoff procedure) published on the airfield. The list of airfields impacted and their associated TMA is known.
- The “LEAVING PROCEDURE” procedures are known.
- By way of example, in 2002, the procedures to be employed in emergency situations for the AGEN airfield are as follows:
-
- in the event of MISSED APPR (Missed Approach), climb in track to 1000 ft, then continue the climb by intercepting and following the DME ARC 27 NM from the VORDME AGN up to 3500 ft, then turn right, direction of the NDB AG
- “LEAVING PROCEDURE”: in the event of 2 consecutive landing failures, leave the TMA by SID SECHE1W at the MSA
- On departure: continue the procedure up to the limits of the TMA, at the last assigned flight level, then climb to the CRZ FL.
- All the procedures to follow in order to cleanly pull out of traffic and terminal areas, explained in the examples above, can be expressed in electronic flight plan terms and followed. As the examples demonstrate, there is a relatively wide margin of maneuver for most of these procedures, at the same time enabling optimization in terms of traffic, weather and performances, which the invention provides. The invention is also applicable to other emergency procedures such as:
-
- a depressurization emergency: Emergency descent, defined in ICAO document DOC 7030. In this case, it is stipulated that the airplane must “be placed aside” i.e. deviate from its route, then wait for ATC instructions.
- Engine failure on ETOPS certified twin engine aircraft: no ICAO standards, but manufacturers' recommendations for constructing a diversionary flight plan to the nearest ETOPS airport when an engine failure is detected ‘en route’ over the ocean.
- The automation of these procedures requires significant interaction with the flight plan and path preparation functions. The computer processing module for implementing the invention consists of a software module capable of being executed on a standard FMS computer such as the THALES AVIONICS NEW FMS, currently flying on the whole Airbus product range (redundant computer). . . . The source program will advantageously be programmed in ADA or C complying with the standards to be observed for the code to be able to be certified.
- The process coded by the program ensures the selection of procedures, examples of which have been given above, in the computer database of procedures, prepares an optimized flight path in case of emergency (engine failure, loss of communications, etc.), based on the emergency procedures database, the airspaces crossed, the airplane's performances, traffic, weather, relief, ensures the progress of this flight path and the sending of the flight path to the ground, if air-to-ground communication via Datalink is possible.
-
FIG. 2 shows the communication links of adrone 30. The loss of the communication link between control and the drone poses a problem since the pilot on the ground no longer receives control instructions. Likewise, the loss of the communication link between the drone and the ground station means that the pilot on the ground is no longer aware of the “voice” instructions from the control centre. Depending upon which FMS functions are divided between ground and air and upon which of the communication links are lost, the pilot will or will not intervene in the execution of the procedures. In the extreme, in the event that all the links (ATC, ground station) are lost both ways, the proposed device and system enable fully automatic execution, on condition that all the necessary FMS functions are on board. The choice of optimum architecture must be made according to prescribed operational use conditions, taking into account the constraints of weight, space requirement and cost which lead to a transfer of computing power towards the ground station. - In the “manned aircraft” case, the process may further offer a number of strategies to the crew, enabling them to choose between several flight paths, observing all the regulations, but optimizing different criteria.
- The preference function, also applicable in the case of unmanned aircraft, will most often favor enhanced safety in terms of minimum separation from other aircraft and relief elements, but it is easy to construct a preference function which will be capable of being programmed according to the operational context. Most often, a second rank optimum obtained by parts will be sufficient. However, if the operational context calls for it, nothing prevents seeking a complete solution for the preference function optimum, on condition that the necessary computing power is available.
- There are three main modes of embodiment of the invention, according to whether the aircraft is ‘en route’, on takeoff or on approach.
- The main elements of the process in the “En Route” case are specified below.
- The FMS may extend cruising if necessary to keep a 20 min segment in front of the aircraft at constant level. It erases any STEPS that may be present in front of the aircraft in the 20 min interval. The FMS uses the “Constant Mach Segment” function on the points in front of the aircraft, at least over the predicted 20 mins, for flying at constant speed. In the event of terrain conflict, based on the MORA (Minimum Off Route Altitude), the FMS computes and inserts a “STEP CLIMB” in front of the aircraft to be 2000 feet above the highest MORA in the 20 min interval. Laterally, the FMS follows the active flight plan, but modifying the transitions (turns) between portions of the flight plan to remain compatible with the airplane speed. After said 20 mins, the FMS returns to the preprogrammed vertical flight plan, as well as to the preprogrammed speed by canceling the STEP and CMS that may have been entered in the first 20 min phase.
- Then the FMS vertically controls the aircraft to follow the end-of-cruise and descent flight plan up to the approach point required by the procedure, namely the recommended beacon (if ICAO) or another point such as the IAF in France. This means full authority of the FMS over flight controls and thrust, as well as any surfaces. During its descent towards the chosen navigation aid, the FMS inserts a holding pattern in its flight plan, adopting the assumptions explained below.
- If a HOLD is defined in the navigation database on the beacon or the IAF, the FMS inserts this HOLD; otherwise, it utilizes the HOLD function, with the following parameter settings:
-
- Speed given by DO 236B according to altitude and weight category,
- Bearing with respect to north, parallel to the arrival segment on the beacon/IAF,
- Default steering: Right,
- Length of the right portion: 1 minute.
- An altitude constraint equal to the recommended minimum altitude over the beacon/IAF or equal to the next altitude constraint of the Intermediate part of the approach is inserted on the HOLD, while being raised by a possible MSA (Minimum Sector Altitude).
- The FMS uses the “IMMEDIATE EXIT” function to exit the holding pattern when it predicts an arrival time compatible with the initially planned time, and adjusts the initiation of the function to ensure a landing within the 30 mins around the planned time.
- In final approach, if an instrument approach was present in the FMS active flight plan, it follows this approach up to the landing; if no approach was entered, the FMS carries out the following procedure:
-
- Test of the frequencies of the radionavigation means to detect the runways in use, by taking the ILS, MLS, GLS, VORDME, NDB signals in order
- Insertion of the runway which i)contains an ILS into the flight plan, or failing this, in order a MLS, GLS, VORDME, NDB, ii) is located by the aircraft (to avoid runway crossings)
- Following the flight plan up to the landing
- If all the tests are negative, stringing into the flight plan a “Runway by itself” approach (Autonomous Runway approach, only containing the runway and a half right in the runway track, from the runway threshold, on which the airplane may be guided) in the direction opposite to the wind measured on board and following this approach.
- The other systems (Transponders) may transmit signals such as “TRANSMITTING BLIND”, code 7700, according to the type of failure.
- This process will be adapted to take into account the specific features of each state/region. Thus, in Europe, the above 20 mins are replaced by 7 mins (Regional Supplementary Procedure Doc 7030/4).
- An example of embodiment of this ‘En Route’ case is described in detail for the flight plan in
FIG. 4 which is located in the Brétigny sector. The processing flow chart inFIG. 3 shows the applicable steps of the procedure, which are described herebelow. -
Step 1, (410, 420, 430): on detecting the failure: FMS: -
- Calculation of the flight path hold segment for a given time originating from the BDP, possibly raised by MORAs originating from the BDN and FMS;
- Level and speed adjustment (transition to Managed at the current speed) Recalculation of the lateral flight plan with the current speed
- Following this short term flight plan
- The FMS checks to see whether there is a “hold time” in the current geographical area in the BDP. If so, it applies this time, if not, the ICAO value of 20 mins is used. In the example, a time of 7 mins is found and will be applied. During this period, the FMS freezes the speed of the aircraft at the current value and the level at the current level. The FMS calculates a rejoin onto the active flight plan by creating an orthogonal projection of the airplane onto it to identify the rejoin segment and making a turn whose angle optimizes the clearance with other aircraft. For this, one possibility is to test for a rejoin every 5°, between an intercept at 45° and an intercept at 90°; for each rejoin value. The FMS looks to see whether the other surrounding aircraft will cut across the rejoin track with a vertical clearance of less than 500 feet; for aircraft that cut across the rejoin segment, the FMS extrapolates the position of these aircraft from the speed and heading data obtained by interrogating the MODE S transponder of the aircraft in question (TCAS or ADS-B function); the FMS then compares the passage times of the aircraft that cut across the track with its passage times at the same point. The solution is the rejoin that maximizes the time deltas between the drone and the passing aircraft.
- In the case of
FIG. 4 , the rejoin 310, which is the optimum solution, is that which makes an angle of 45° with the flight path. - Once the rejoin lateral flight path is obtained, the FMS checks the value of the MORAs from the BDN and where necessary adjusts the flight level, then it checks the absence of conflict in the vertical plane with other aircraft, at the level in question. If a conflict is detected, the algorithm loops back until it finds a solution.
-
Step 2, 440: Return to the managed vertical and speed after “hold time”. - If phase=CRZ, following the cruise flight plan up to (T/D): If phase=DES, following 3D flight plan up to the approach point originating from the BDP; control of surfaces, thrust, landing gear.
- One possible calculation algorithm is as follows: If the FMS predicts a rejoin onto the flight plan over a period greater than “hold time”, it remains at constant speed and level until the rejoin, then goes back to “managed Speed and Vertical”, that is, at the optimum level and speed calculated by the FMS; if the FMS predicts a rejoin before elapse of “hold time”, it continues on the flight plan until reaching the “hold time”, then goes back into “managed Speed and Vertical”; on arriving at the end-of-cruise point (T/D), the FMS reassigns the descent level to that of the approach point originating from the BDP and engages the descent.
-
Step 3, 450: Insertion of a HOLD at the approach point, and constraint at this point to remain above the relief (raised by the MSA). - The FMS inserts a HOLD at the approach point of the BDP in the following way: If a HOLD already exists at the approach point, the FMS uses this HOLD; otherwise, if a HOLD is coded in BDN at this point, the FMS inserts this HOLD; otherwise, the FMS inserts a HOLD with a right turn, length of
right leg 1 min, ICAO speed. At the point of entry and exit of the HOLD, the FMS inserts an altitude constraint equal to the MSA retrieved from the BDP if it exists. Otherwise, the FMS inserts a constraint equal to the value of the ILS GLIDE beam intercept if it exists, and, if not, constructs a default approach and inserts a constraint equal to the deceleration level on this approach. - Step 4, 460: Optimization of the moment of exit from HOLD to land closest to the initially estimated time, and at the maximum in the next 30 mins.
- If the projected landing weight is admissible for the runway, the FMS flies the HOLD until the predicted landing time matches the initially estimated time; otherwise, the FMS uses the 30 min slot until a landing weight is attained below the threshold authorized on the runway; in any case, at the end of 30 mins deviation from the estimated time, the FMS exits the HOLD and continues the approach.
-
Step 5, 470: Determination of the landing procedure - If entered before the failure, use of the entered procedure, otherwise choice optimizing the ground means. A possible algorithm is the following: If a procedure is coded before detection of the failure, the FMS follows this procedure; if no procedure is coded, the FMS searches for the approach procedure that maximizes precision, taking its on-board means into account. It will use in order: ILS, MLS, GLS, FLS, GPS, VOR/DME; if no approach is possible with the above means, the FMS produces a “Runway by itself” approach by stringing a segment in the runway track, with −3° of slope over 5 NM, on the opposite side to the wind. In any case, if the FMS detects a radionavigation means failure for carrying out the approach in question, it changes over to the “emergency landing procedure” algorithm explained in the corresponding example of embodiment. The FMS controls the extension of slats, flaps and landing gear on the approach, as the pilot would do, when it reaches the associated characteristic speeds.
- The main elements of the process in the “On Takeoff” case are specified below. The procedures described are those to be employed in the event of communication failure only. There are other very different procedures for dealing with cases of engine failure, etc.
- In the event of a situation of initiating an emergency procedure due to a communication failure on takeoff, almost all the procedures to be employed are of the type: “Continue flying up to the limit of the TMA, following the SID procedure at the last allocated altitude, or if this is not compatible with the existing obstacles, position yourself at the minimum safety altitude. Then, climb to the cruise altitude indicated by the active flight plan.” This very common type of procedure may be expressed in the following way in a flight management system: Aircraft in MANAGE (fully automatic control); insertion of an “AT OR BELOW” altitude constraint at the SID points, equal to the last level assigned by control, where applicable raised by the MSA (avoidance of an obstacle); holding at this level until the geographical limits of the TMA, to be coded into a database; return to the FMS active flight plan, which will automatically switch over to climbing up to cruise level entered on the ground; application of the “En Route” procedure described above.
- According to the regions/states/airfields, adjustments marked on the maps may be necessary. They are coded into the BDP.
- This “On Takeoff” mode of embodiment is illustrated by the example in
FIG. 6 . The aircraft is down below and has just taken off. The active flight plan passes through the points WP1 . . . WP5. Points WP1 . . . WP4 are the points of the SID, and point WP5 is the first point of the “EN ROUTE” part. The “comm failure” flight plan stored in BDP, passes through WP1, WP6, WP7. - The hexagon represents the TMA.
- The processing flow chart of this mode of embodiment for this example is that in
FIG. 5 . - By calling up the BDP, the FMS loads the “Emergency Situation” flight plan applicable to the emergency situation detected in the current phase. The FMS loads the coordinates of the characteristic points of the TMA and determines the first point outside of the TMA on the active flight plan (here WP5). The FMS strings the “Emergency Situation” flight plan onto this first point, minimizing the distance and following the outlines of the TMA; the following is a possible algorithm: A margin of X NM (5 NM for example) is determined with respect to the polyhedron, at the level of the polyhedron break points, a point is created on the bisector segment, 5 NM from the outline; then these points are connected up to WP5; this calculation is made starting from both the left and the right, at the end of the “Emergency Situation” flight plan and the one with the least distance is kept.
- At the vertical profile level, “AT OR ABOVE” altitude constraints are inserted on the points of this flight plan at the value of the MSA of the sector originating from the BDN on the “Emergency Situation” starting procedure points. The FMS assigns a cruise level equal to the last level obtained from control. No constraint is inserted on the last starting procedure point (here WP7), just as on the next EN ROUTE points (here WP5), so that the climb profile is calculated to climb to the cruise level, i.e. to the last level assigned by control. The FMS guides along this flight plan then passes onto the “En Route Emergency Situation” part.
- The main elements of the process in the “On Approach” case are specified below. The procedures described are those to be employed in the event of communication failure only. There are other very different procedures for dealing with cases of engine failure, etc.
- In the event of communication failure on landing, it is generally required to employ the missed approach (MISSED APPROACH) procedure, then in the event of repeated failure, to employ the “LEAVING PROCEDURE”. “LEAVING PROCEDURES” are almost always instructions for following SID and radials towards predetermined beacons. For example, for NICE (France) “After missed approach, climb to 2500 feet and then leave the Nice TMA at 2500 feet in the VOR “NIZ” R-126 direction. The coding of this procedure in the FMS is possible via the addition of ARINC 424 legs, of the CA 2500 type (“Course to an altitude equal to 2500 feet”), followed by a CR 126NIZ leg (“Course to a RADIAL 126° MAG from VOR “NIZ”), and can therefore be included in the aircraft's navigation database. All the procedures for leaving the TMA can be coded in a database. What the FMS has to do is to create a new type of link between the end of the missed approach and this procedure. This “On Approach” mode of embodiment is illustrated by the example in
FIG. 8 where the NANTES TMA is shown. The procedure is: “In the case where the pilot has no knowledge of the runway in use, employ the procedure for RWY03 (A circle before landing may be necessary if the wind observed by the pilot indicates that RWY21 is in use). In the event of a missed approach, employ the corresponding published procedure and begin a second approach. If the second approach fails, follow the applicable corresponding procedure then leave the TMA at 3000 feet and try to attain VMC”. - The processing flow chart of this example of embodiment is given in
FIG. 7 . - In the case of the drone, there is no possibility of following the visual conditions procedure (VMC) since the pilot cannot “see” the runway. A possible algorithm will therefore be: If a complete approach has been entered before the “Emergency Situation”, the FMS follows the procedure described in the “En Route Emergency Situation” part, starting from
step 5; if no runway has been entered, the FMS retrieves the possible landing runways from the BDP (here RWY03 or 21) and determines the runway in use thanks to the wind. In the absence of wind, the FMS uses the runway recommended in the BDP (here RWY03); the FMS then switches over to step 5 of the “En Route”part to determine the best radionavigation means for landing on this runway. If the “Emergency Situation” is initiated during a go-around (Missed Approach), i.e. while the pilot on the ground is performing a go-around, then the FMS retrieves the “Emergency Situation” flight plan from the BDP (here continuation of the Missed Approach then attempt at second approach. The FMS then switches over to step 5 of the “En Route” part to determine the best radionavigation means for landing on this runway. In the case of the drone, the LEAVING TMA procedure is not employed since VMC conditions are inapplicable. The drone will continue its approaches until it succeeds in one, even if it must lead to damage to the craft. - In the case of a manned aircraft, the process may follow the procedure to the end. The FMS will therefore offer to follow the same routing as above and, in the event of a 2nd landing failure, will retrieve the TMA polyhedron from the BDP, string a straight line to the last Missed Approach point in the axis of this last segment up to the TMA limit, possibly constraining the created points in altitude (here 3000 feet). In the event of a succession of missed approaches, the last emergency procedure will normally be the intervention of fighter planes which will guide the aircraft in its landing.
- For a manned aircraft, this will spare some time for the ground control center to initiate a repartition of the craft by fighter planes. A drone as already mentioned, will attempt to land whatever the cost, including damages.
- The procedures described here are those to be applied only in case of communication failure. There are other very different procedures to address the situation like engine failure of the emergency situations.
- In the event of communication failure on landing, it is generally required to employ the missed approach (MISSED APPROACH) procedure, then in the event of repeated failure, to employ the “LEAVING PROCEDURE”. “LEAVING PROCEDURES” are almost always instructions for following SID and radials towards predetermined beacons. For example, for NICE (France) “After missed approach, climb to 2500 feet and then leave the Nice TMA at 2500 feet in the VOR “NIZ” R-126 direction. The coding of this procedure in the FMS is possible via the addition of ARINC 424 legs, of the CA 2500 type (“Course to an altitude equal to 2500 feet”), followed by a CR 126NIZ leg (“Course to a RADIAL 126° MAG from VOR “NIZ”), and can therefore be included in the aircraft's navigation database. All the procedures for leaving the TMA can be coded in a database. What the FMS has to do is to create a new type of link between the end of the missed approach and this procedure. This “On Approach” mode of embodiment is illustrated by the example in
FIG. 8 where the NANTES TMA is shown. The procedure is: “In the case where the pilot has no knowledge of the runway in use, employ the procedure for RWY03 (A circle before landing may be necessary if the wind observed by the pilot indicates that RWY21 is in use). In the event of a missed approach, employ the corresponding published procedure and begin a second approach. If the second approach fails, follow the applicable corresponding procedure then leave the TMA at 3000 feet and try to attain VMC”. - The processing flow chart of this example of embodiment is given in
FIG. 7 . - In the case of the drone, there is no possibility of following the visual conditions procedure (VMC) since the pilot cannot “see” the runway. A possible algorithm will therefore be: If a complete approach has been entered before the “Emergency Situation”, the FMS follows the procedure described in the “En Route Emergency Situation” part, starting from
step 5; if no runway has been entered, the FMS retrieves the possible landing runways from the BDP (here RWY03 or 21) and determines the runway in use thanks to the wind. In the absence of wind, the FMS uses the runway recommended in the BDP (here RWY03); the FMS then switches over to step 5 of the “En Route”part to determine the best radionavigation means for landing on this runway.
Claims (21)
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0512423A FR2894368B1 (en) | 2005-12-07 | 2005-12-07 | DEVICE AND METHOD FOR AUTOMATED CONSTRUCTION OF EMERGENCY TRACK FOR AIRCRAFT |
FR0512423 | 2005-12-07 |
Publications (2)
Publication Number | Publication Date |
---|---|
US20070129855A1 true US20070129855A1 (en) | 2007-06-07 |
US8521340B2 US8521340B2 (en) | 2013-08-27 |
Family
ID=36968642
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/567,948 Expired - Fee Related US8521340B2 (en) | 2005-12-07 | 2006-12-07 | Device and method of automated construction of emergency flight path for aircraft |
Country Status (5)
Country | Link |
---|---|
US (1) | US8521340B2 (en) |
EP (1) | EP1796060B1 (en) |
CA (1) | CA2569947A1 (en) |
DE (1) | DE602006012157D1 (en) |
FR (1) | FR2894368B1 (en) |
Cited By (122)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040245408A1 (en) * | 2003-03-19 | 2004-12-09 | Airbus France | Method and device to assist in the piloting of an aircraft in a non-precision approach during a landing phase |
US20070219679A1 (en) * | 2006-03-14 | 2007-09-20 | Thales | Method of assisting in the navigation of an aircraft with an updating of the flight plan |
US20080167885A1 (en) * | 2007-01-10 | 2008-07-10 | Honeywell International Inc. | Method and system to automatically generate a clearance request to deivate from a flight plan |
US20080177432A1 (en) * | 2006-10-10 | 2008-07-24 | Thales | Method of forming a 3d safe emergency descent trajectory for aircraft and implementation device |
US20080243315A1 (en) * | 2007-02-07 | 2008-10-02 | Airbus France | Device and method for assisting in the management of an engine failure on an aircraft |
US20080294307A1 (en) * | 2007-05-22 | 2008-11-27 | The Boeing Company | Aircraft Guidance Using Localizer Capture Criteria for Rectilinear Displacement Data |
US20090005918A1 (en) * | 2007-05-02 | 2009-01-01 | Thales | Method for optimizing the exit of an aircraft in a holding circuit |
US20090030564A1 (en) * | 2007-07-26 | 2009-01-29 | Mark Alan Peterson | Method and apparatus for managing instrument missed approaches |
US20090027253A1 (en) * | 2007-07-09 | 2009-01-29 | Eads Deutschland Gmbh | Collision and conflict avoidance system for autonomous unmanned air vehicles (UAVs) |
US20090089693A1 (en) * | 2007-10-02 | 2009-04-02 | Honeywell International Inc. | Method of producing graphically enhanced data communications |
US20090125236A1 (en) * | 2007-03-13 | 2009-05-14 | Thales | Method for reducing nuisance alarms for anti-collision with obstacles on aircraft |
US20090157288A1 (en) * | 2007-12-12 | 2009-06-18 | The Boeing Company | Air Traffic Control Delay Factor |
US20100017114A1 (en) * | 2007-05-24 | 2010-01-21 | Honeywell International Inc. | Flight Path Planning to Reduce Detection of an Unmanned Aerial Vehicle |
US20100017053A1 (en) * | 2007-05-22 | 2010-01-21 | The Boeing Company | Consistent Localizer Captures |
US7681832B2 (en) | 2007-05-02 | 2010-03-23 | Honeywell International Inc. | Ducted fan air vehicle with deployable wings |
US20100082186A1 (en) * | 2008-09-29 | 2010-04-01 | Honeywell International Inc. | Methods and systems for indicating whether an aircraft is below a minimum altitude criterion for a sector |
US20100108809A1 (en) * | 2008-10-31 | 2010-05-06 | Honeywell International Inc. | Noise-suppressing strut support system for an unmanned aerial vehicle |
US20100121575A1 (en) * | 2006-04-04 | 2010-05-13 | Arinc Inc. | Systems and methods for aerial system collision avoidance |
US20100161156A1 (en) * | 2008-12-23 | 2010-06-24 | Thales | Device for assisting in the choice of a diversion airport |
US20100187369A1 (en) * | 2009-01-26 | 2010-07-29 | Honeywell International Inc. | Ducted fan uav control alternatives |
US20100256839A1 (en) * | 2009-04-02 | 2010-10-07 | Honeywell International Inc. | Performing Corrective Action on Unmanned Aerial Vehicle Using One Axis of Three-Axis Magnetometer |
US20100274419A1 (en) * | 2009-04-28 | 2010-10-28 | Thales | Method and Device for Adjusting the Trajectory of an Aircraft in a Climb Circuit |
US20110001017A1 (en) * | 2008-12-08 | 2011-01-06 | Honeywell International Inc. | Uav ducted fan swept and lean stator design |
WO2011024189A2 (en) * | 2009-07-20 | 2011-03-03 | Airbus Engineering Centre India | System and method for computing flight time from an equi- distance point to a reference point |
US7904213B2 (en) | 2006-03-14 | 2011-03-08 | Thales | Method of assisting in the navigation of an aircraft with an updating of the flight plan |
US20110095530A1 (en) * | 2009-10-26 | 2011-04-28 | Honeywell International Inc. | Tethered aquatic device with water power turbine |
US8024078B2 (en) | 2007-04-25 | 2011-09-20 | Thales | System for aiding the taxiing of an aircraft |
US20110231036A1 (en) * | 2010-03-22 | 2011-09-22 | Honeywell International Inc. | Aircraft communications radio tuning aid system and method |
US8109711B2 (en) | 2008-07-18 | 2012-02-07 | Honeywell International Inc. | Tethered autonomous air vehicle with wind turbines |
US8126599B2 (en) | 2007-04-20 | 2012-02-28 | Thales | Method of calculating approach trajectory for aircraft |
US8190310B2 (en) | 2008-02-08 | 2012-05-29 | Thales | Methods of optimizing the location of an aircraft on the ground and in the take-off and landing phases |
US20120143482A1 (en) * | 2010-12-02 | 2012-06-07 | Honeywell International Inc. | Electronically file and fly unmanned aerial vehicle |
US20120215384A1 (en) * | 2009-10-30 | 2012-08-23 | Emerald Sky Technologies, LLC | Flight Control System with Dynamic Allocation of Functionality Between Flight Crew and Automation |
US20120221175A1 (en) * | 2011-02-28 | 2012-08-30 | The Boeing Company | Alternative communications for an air vehicle |
US8275499B2 (en) | 2008-10-17 | 2012-09-25 | Thales | Device for calculating a flight plan of an aircraft |
US20130066489A1 (en) * | 2011-09-08 | 2013-03-14 | Andrew Robert Hooks | Consistent Localizer Captures |
US20130211702A1 (en) * | 2012-02-15 | 2013-08-15 | Cipriano A. Santos | Allocation of flight legs to dispatcher positions |
US8521340B2 (en) * | 2005-12-07 | 2013-08-27 | Thales | Device and method of automated construction of emergency flight path for aircraft |
US8615337B1 (en) * | 2008-09-25 | 2013-12-24 | Rockwell Collins, Inc. | System supporting flight operations under instrument meteorological conditions using precision course guidance |
US20140032103A1 (en) * | 2012-07-26 | 2014-01-30 | Ge Aviation Systems Llc | Method of displaying a flight plan |
US8798815B1 (en) | 2013-03-13 | 2014-08-05 | Honeywell International Inc. | System and method alerting an aircrew of threshold altitudes |
US8843303B1 (en) * | 2012-12-17 | 2014-09-23 | Rockwell Collins, Inc. | Risk-aware contingency flight re-planner system and related method |
US20140288730A1 (en) * | 2013-03-19 | 2014-09-25 | The Boeing Company | Method of Flying an Unmanned Aerial Vehicle |
US20140309821A1 (en) * | 2013-04-11 | 2014-10-16 | Airbus Operations SAS (France) | Aircraft flight management devices, systems, computer readable media and related methods |
US20150005992A1 (en) * | 2013-06-28 | 2015-01-01 | Thales | Method and device for calculating a flight plan of an aircraft in a runway approach phase |
CN104260896A (en) * | 2014-09-01 | 2015-01-07 | 陈宜中 | Method for passengers to participate in alarming when passenger plane meets with hijacking |
US9004393B2 (en) | 2010-10-24 | 2015-04-14 | University Of Kansas | Supersonic hovering air vehicle |
US20150145954A1 (en) * | 2013-11-27 | 2015-05-28 | Honeywell International Inc. | Generating a three-dimensional model of an industrial plant using an unmanned aerial vehicle |
US9052198B2 (en) | 2011-11-29 | 2015-06-09 | Airbus Operations (S.A.S.) | Interactive dialog device between an operator of an aircraft and a guidance system of said aircraft |
US9087451B1 (en) | 2014-07-14 | 2015-07-21 | John A. Jarrell | Unmanned aerial vehicle communication, monitoring, and traffic management |
US20150266591A1 (en) * | 2013-07-10 | 2015-09-24 | Airbus Helicopters | Method and a device for issuing terrain avoidance warnings for a rotary wing aircraft |
US9174725B2 (en) | 2013-01-11 | 2015-11-03 | Airbus Operations (S.A.S.) | Systems for tasks guidance of operations management in an aircraft cockpit |
US9199724B2 (en) | 2013-05-15 | 2015-12-01 | Honeywell International Inc. | System and method for performing an aircraft automatic emergency descent |
US20150346986A1 (en) * | 2014-05-27 | 2015-12-03 | Thales | Device and method for generating at least one computer file for producing a graphic interface of an electronic equipment, and related computer program product |
US20150379875A1 (en) * | 2014-06-27 | 2015-12-31 | The Boeing Company | Automatic aircraft monitoring and operator preferred rerouting system and method |
US9280904B2 (en) | 2013-03-15 | 2016-03-08 | Airbus Operations (S.A.S.) | Methods, systems and computer readable media for arming aircraft runway approach guidance modes |
US20160180716A1 (en) * | 2014-12-23 | 2016-06-23 | Thales | Method and system for guidance of an aircraft |
US9424755B2 (en) | 2014-09-30 | 2016-08-23 | The Boeing Company | Flight analogous and projection system |
US9443434B2 (en) | 2014-09-30 | 2016-09-13 | The Boeing Company | Flight path discontinuities |
US20160299231A1 (en) * | 2013-11-11 | 2016-10-13 | Airbus Defence Ang Space Gmbh | Aircraft navigation system and method of navigating an aircraft |
US20160343257A1 (en) * | 2015-05-18 | 2016-11-24 | The Boeing Company | Aircraft flight control using a required time of arrival index |
US9508264B2 (en) * | 2014-09-30 | 2016-11-29 | Elwha Llc | System and method for management of airspace for unmanned aircraft |
US9530320B2 (en) | 2014-09-30 | 2016-12-27 | The Boeing Company | Flight object communications system |
US20170076612A1 (en) * | 2014-04-25 | 2017-03-16 | Sony Corporation | Information processing device, information processing method, program, and imaging system |
EP3151080A1 (en) * | 2015-09-29 | 2017-04-05 | Airbus Defence and Space GmbH | Unmanned aircraft and method for secure landing of an unmanned aircraft |
EP3163394A1 (en) * | 2015-10-30 | 2017-05-03 | Xiaomi Inc. | Method and device for controlling an unmanned aerial vehicle |
US9697737B2 (en) | 2014-09-30 | 2017-07-04 | The Boeing Company | Automatic real-time flight plan updates |
US20170197710A1 (en) * | 2015-09-07 | 2017-07-13 | Tao Ma | Passenger transport systems based on pilotless vertical takeoff and landing (vtol) aircraft |
US9866313B1 (en) | 2016-12-14 | 2018-01-09 | T-Mobile Usa, Inc. | UAV cellular communication service delivery |
US9878787B2 (en) | 2015-07-15 | 2018-01-30 | Elwha Llc | System and method for operating unmanned aircraft |
US9878786B2 (en) | 2014-12-04 | 2018-01-30 | Elwha Llc | System and method for operation and management of reconfigurable unmanned aircraft |
US9902491B2 (en) | 2014-12-04 | 2018-02-27 | Elwha Llc | Reconfigurable unmanned aircraft system |
US9994315B2 (en) * | 2015-07-16 | 2018-06-12 | Physio-Control, Inc. | Unmanned aerial vehicles in medical applications |
US10019905B1 (en) * | 2017-03-24 | 2018-07-10 | The Boeing Company | Aircraft holding pattern analysis system and method |
US10020872B2 (en) * | 2016-10-11 | 2018-07-10 | T-Mobile Usa, Inc. | UAV for cellular communication |
US10026324B2 (en) | 2014-11-04 | 2018-07-17 | Honeywell International Inc. | Systems and methods for enhanced adoptive validation of ATC clearance requests |
US10074284B1 (en) * | 2016-06-10 | 2018-09-11 | ETAK Systems, LLC | Emergency shutdown and landing for unmanned aerial vehicles with air traffic control systems |
US10121384B2 (en) * | 2014-09-30 | 2018-11-06 | The Boeing Company | Aircraft performance predictions |
US10175699B2 (en) * | 2015-07-16 | 2019-01-08 | Safran Electronics And Defense | Method for automatically assisting with the landing of an aircraft |
EP2498055B1 (en) | 2010-09-14 | 2019-01-23 | The Boeing Company | Management System for Unmanned Aerial Vehicles |
CN109444806A (en) * | 2018-10-15 | 2019-03-08 | 中海油信息科技有限公司 | Offshore drilling platforms helicopter navigation frequency multiplex system and method |
US10228694B2 (en) * | 2016-03-04 | 2019-03-12 | Animusoft Corporation | Drone and robot control systems and methods |
US10284525B2 (en) * | 2016-07-11 | 2019-05-07 | Honeywell Lntemational Inc. | Cross-domain data-gate for secure transmission of data over publicly shared datalinks |
US10319030B1 (en) | 2018-11-09 | 2019-06-11 | Capital One Services, Llc | Systems and methods for automatic route re-determination for an unmanned aerial vehicle |
US10341011B2 (en) * | 2015-08-13 | 2019-07-02 | Bae Systems Plc | Apparatus and method for communications management |
US10417917B2 (en) | 2016-03-08 | 2019-09-17 | International Business Machines Corporation | Drone management data structure |
US10423831B2 (en) | 2017-09-15 | 2019-09-24 | Honeywell International Inc. | Unmanned aerial vehicle based expansion joint failure detection system |
US10529221B2 (en) | 2016-04-19 | 2020-01-07 | Navio International, Inc. | Modular approach for smart and customizable security solutions and other applications for a smart city |
US10540900B2 (en) * | 2016-03-08 | 2020-01-21 | International Business Machines Corporation | Drone air traffic control and flight plan management |
DE102018218715A1 (en) * | 2018-10-31 | 2020-04-30 | Airbus Defence and Space GmbH | Method for operating an at least temporarily unmanned aircraft and such an aircraft |
US10689107B2 (en) | 2017-04-25 | 2020-06-23 | International Business Machines Corporation | Drone-based smoke detector |
US10720066B2 (en) | 2016-06-10 | 2020-07-21 | ETAK Systems, LLC | Flying lane management with lateral separations between drones |
CN111522354A (en) * | 2019-02-01 | 2020-08-11 | 中强光电股份有限公司 | Unmanned aerial vehicle and failure safety method thereof |
CN111552310A (en) * | 2019-02-08 | 2020-08-18 | 沃科波特有限公司 | Aircraft and motion planning method and system thereof |
US10789853B2 (en) | 2016-06-10 | 2020-09-29 | ETAK Systems, LLC | Drone collision avoidance via air traffic control over wireless networks |
US10824170B2 (en) | 2013-11-27 | 2020-11-03 | Aurora Flight Sciences Corporation | Autonomous cargo delivery system |
US10899444B2 (en) | 2016-03-08 | 2021-01-26 | International Business Machines Corporation | Drone receiver |
US10922983B2 (en) | 2016-03-08 | 2021-02-16 | International Business Machines Corporation | Programming language for execution by drone |
EP3799010A1 (en) * | 2019-09-25 | 2021-03-31 | Honeywell International Inc. | Complete loss of engine thrust aircraft guidance to runway system and method |
US11138892B2 (en) | 2017-12-19 | 2021-10-05 | Honeywell International Inc. | TCAS coupled FMS |
US11183072B2 (en) | 2016-03-08 | 2021-11-23 | Nec Corporation | Drone carrier |
US11250709B2 (en) | 2016-06-10 | 2022-02-15 | Metal Raptor, Llc | Drone air traffic control incorporating weather updates |
US11263909B2 (en) | 2016-06-10 | 2022-03-01 | Metal Raptor, Llc | Air traffic control of passenger drones concurrently using a plurality of wireless networks |
US11282399B2 (en) * | 2016-02-29 | 2022-03-22 | Garmin International, Inc. | Emergency autoland system |
US11328613B2 (en) | 2016-06-10 | 2022-05-10 | Metal Raptor, Llc | Waypoint directory in air traffic control systems for passenger drones and unmanned aerial vehicles |
US11341858B2 (en) | 2016-06-10 | 2022-05-24 | Metal Raptor, Llc | Managing dynamic obstructions in air traffic control systems for passenger drones and unmanned aerial vehicles |
US11355020B2 (en) | 2016-06-10 | 2022-06-07 | Metal Raptor, Llc | Drone air traffic control over wireless networks for package pickup and delivery |
US11403956B2 (en) | 2016-06-10 | 2022-08-02 | Metal Raptor, Llc | Air traffic control monitoring systems and methods for passenger drones |
US11436929B2 (en) | 2016-06-10 | 2022-09-06 | Metal Raptor, Llc | Passenger drone switchover between wireless networks |
US11468778B2 (en) | 2016-06-10 | 2022-10-11 | Metal Raptor, Llc | Emergency shutdown and landing for passenger drones and unmanned aerial vehicles with air traffic control |
US11488483B2 (en) | 2016-06-10 | 2022-11-01 | Metal Raptor, Llc | Passenger drone collision avoidance via air traffic control over wireless network |
US11551564B2 (en) * | 2012-12-28 | 2023-01-10 | Otto Aero Company | Aircraft with landing system |
US11573579B1 (en) * | 2022-05-23 | 2023-02-07 | Zhuhai Xiangyi Aviation Technology Company Ltd. | Method, system, and device for planning path for forced landing of aircraft based on image recognition |
US20230129329A1 (en) * | 2021-10-25 | 2023-04-27 | Aurora Flight Sciences Coporation, A Subsidiary Of The Boing Company | Guidance modes for an unmanned aerial vehicle |
US11657721B1 (en) * | 2013-08-26 | 2023-05-23 | Otto Aero Company | Aircraft with flight assistant |
US11670180B2 (en) | 2016-06-10 | 2023-06-06 | Metal Raptor, Llc | Obstruction detection in air traffic control systems for passenger drones |
US11670179B2 (en) | 2016-06-10 | 2023-06-06 | Metal Raptor, Llc | Managing detected obstructions in air traffic control systems for passenger drones |
US11710412B1 (en) * | 2022-09-23 | 2023-07-25 | Sichuan University | Method and device for flight path planning considering both the flight trajectory and the visual images from air traffic control systems for air traffic controllers |
US11710414B2 (en) | 2016-06-10 | 2023-07-25 | Metal Raptor, Llc | Flying lane management systems and methods for passenger drones |
US11722462B1 (en) * | 2022-04-28 | 2023-08-08 | Beta Air, Llc | Systems and methods for encrypted flight plan communications |
US11727813B2 (en) | 2016-06-10 | 2023-08-15 | Metal Raptor, Llc | Systems and methods for air traffic control for passenger drones |
EP4276792A3 (en) * | 2022-04-19 | 2024-02-28 | Rockwell Collins, Inc. | Autonomous air traffic control interaction |
Families Citing this family (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP2040137B1 (en) | 2007-09-21 | 2012-05-16 | The Boeing Company | Predicting aircraft trajectory |
FR2947067B1 (en) * | 2009-06-23 | 2011-08-19 | Thales Sa | METHOD AND DEVICE FOR OPTIMIZING THE DECELERATION POINT OF A WAITING CIRCUIT |
US9257048B1 (en) | 2010-04-21 | 2016-02-09 | The Boeing Company | Aircraft emergency landing route system |
US9520066B2 (en) * | 2010-04-21 | 2016-12-13 | The Boeing Company | Determining landing sites for aircraft |
US8977484B1 (en) | 2013-08-22 | 2015-03-10 | The Boeing Company | Using aircraft trajectory data to infer aircraft intent |
US9683864B2 (en) * | 2015-02-24 | 2017-06-20 | 168 Productions, LLC | System for providing aircraft landing instructions |
CN107408352B (en) | 2015-03-31 | 2021-07-09 | 深圳市大疆创新科技有限公司 | System and method for geo-fencing device communication |
JP6423521B2 (en) | 2015-03-31 | 2018-11-14 | エスゼット ディージェイアイ テクノロジー カンパニー リミテッドSz Dji Technology Co.,Ltd | System for controlling unmanned aerial vehicles |
US9613537B2 (en) * | 2015-07-29 | 2017-04-04 | The Boeing Company | Multiple landing threshold aircraft arrival system |
US10710710B2 (en) | 2016-10-27 | 2020-07-14 | International Business Machines Corporation | Unmanned aerial vehicle (UAV) compliance using standard protocol requirements and components to enable identifying and controlling rogue UAVS |
US10531994B2 (en) | 2017-01-30 | 2020-01-14 | SkyRyse, Inc. | Safety system for aerial vehicles and method of operation |
US9849044B1 (en) | 2017-01-30 | 2017-12-26 | SkyRyse, Inc. | Vehicle system and method for providing services |
US10228692B2 (en) | 2017-03-27 | 2019-03-12 | Gulfstream Aerospace Corporation | Aircraft flight envelope protection and recovery autopilot |
US10026326B1 (en) * | 2017-07-05 | 2018-07-17 | Honeywell International Inc. | Systems and methods for dynamic selection of advanced approach procedures |
US10535272B2 (en) | 2017-07-27 | 2020-01-14 | SkyRyse, Inc. | System and method for situational awareness, vehicle control, and/or contingency planning |
US11417220B2 (en) | 2018-11-27 | 2022-08-16 | Honeywell International Inc. | Systems and methods for providing an integrated flight management display with interactive time-based functionality |
EP3948328A1 (en) * | 2019-03-29 | 2022-02-09 | BAE SYSTEMS plc | System and method for classifying vehicle behaviour |
US11586196B2 (en) | 2020-01-22 | 2023-02-21 | Honeywell International Inc. | Approach mode activation monitoring function and automatic activation in an event of pilot incapacitation |
CN111414686B (en) * | 2020-03-18 | 2021-01-05 | 北京北特圣迪科技发展有限公司 | Monitoring and early warning system for operating risks of theater mechanical equipment |
FR3110020B1 (en) * | 2020-05-05 | 2023-03-03 | Thales Sa | Method and electronic system for aiding the management of the flight of an aircraft with management of loop(s), associated computer program |
FR3112642B1 (en) * | 2020-07-17 | 2023-03-03 | Thales Sa | Automatic selection of an aircraft flight plan in the approach phase |
Citations (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6633801B1 (en) * | 1999-10-20 | 2003-10-14 | Stanley H. Durlacher | Method and apparatus for providing information to pilots |
US6643580B1 (en) * | 1998-10-16 | 2003-11-04 | Universal Avionics Systems Corporation | Flight plan intent alert system and method |
US6641087B1 (en) * | 2001-10-09 | 2003-11-04 | Cubic Defense Systems, Inc. | Anti-hijacking system operable in emergencies to deactivate on-board flight controls and remotely pilot aircraft utilizing autopilot |
US6658572B1 (en) * | 2001-10-31 | 2003-12-02 | Secure Sky Ventures International Llc | Airline cockpit security system |
US6665631B2 (en) * | 2001-09-27 | 2003-12-16 | The United States Of America As Represented By The Secretary Of The Navy | System and method for measuring short distances |
US20040215372A1 (en) * | 2003-04-22 | 2004-10-28 | Bateman Charles D. | Aircraft autorecovery systems and methods |
US6845302B2 (en) * | 2002-02-07 | 2005-01-18 | Jose Paul Moretto | Airliner irreversible-control anti-hijack system |
US6856864B1 (en) * | 2000-11-17 | 2005-02-15 | Honeywell International Inc. | Method and system for entering data within a flight plan entry field |
US7193520B2 (en) * | 2001-09-27 | 2007-03-20 | Daniel Shear | Anti-hijacking system for airplanes and airports |
US7343239B2 (en) * | 2005-03-24 | 2008-03-11 | Hitachi, Ltd. | Program rewriting system and program rewriting method |
US7437225B1 (en) * | 2005-07-29 | 2008-10-14 | Rockwell Collins, Inc. | Flight management system |
US7837143B2 (en) * | 2005-03-14 | 2010-11-23 | Matos Jeffrey A | Method and apparatus for disabling pilot control of a hijacked aircraft |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5842142A (en) * | 1995-05-15 | 1998-11-24 | The Boeing Company | Least time alternate destination planner |
FR2872316B1 (en) * | 2004-06-29 | 2006-10-06 | Thales Sa | METHOD OF CHANGING THE APPROACH PROCEDURE OF AN AIRCRAFT |
FR2894368B1 (en) * | 2005-12-07 | 2008-01-25 | Thales Sa | DEVICE AND METHOD FOR AUTOMATED CONSTRUCTION OF EMERGENCY TRACK FOR AIRCRAFT |
-
2005
- 2005-12-07 FR FR0512423A patent/FR2894368B1/en not_active Expired - Fee Related
-
2006
- 2006-12-04 CA CA002569947A patent/CA2569947A1/en not_active Abandoned
- 2006-12-05 EP EP06125434A patent/EP1796060B1/en active Active
- 2006-12-05 DE DE602006012157T patent/DE602006012157D1/en active Active
- 2006-12-07 US US11/567,948 patent/US8521340B2/en not_active Expired - Fee Related
Patent Citations (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6643580B1 (en) * | 1998-10-16 | 2003-11-04 | Universal Avionics Systems Corporation | Flight plan intent alert system and method |
US20040111192A1 (en) * | 1998-10-16 | 2004-06-10 | Naimer Hubert L. | Flight plan intent alert system and method |
US6816780B2 (en) * | 1998-10-16 | 2004-11-09 | Universal Avionics Systems Corporation | Flight plan intent alert system and method |
US6633801B1 (en) * | 1999-10-20 | 2003-10-14 | Stanley H. Durlacher | Method and apparatus for providing information to pilots |
US6856864B1 (en) * | 2000-11-17 | 2005-02-15 | Honeywell International Inc. | Method and system for entering data within a flight plan entry field |
US6665631B2 (en) * | 2001-09-27 | 2003-12-16 | The United States Of America As Represented By The Secretary Of The Navy | System and method for measuring short distances |
US7193520B2 (en) * | 2001-09-27 | 2007-03-20 | Daniel Shear | Anti-hijacking system for airplanes and airports |
US6641087B1 (en) * | 2001-10-09 | 2003-11-04 | Cubic Defense Systems, Inc. | Anti-hijacking system operable in emergencies to deactivate on-board flight controls and remotely pilot aircraft utilizing autopilot |
US6658572B1 (en) * | 2001-10-31 | 2003-12-02 | Secure Sky Ventures International Llc | Airline cockpit security system |
US6845302B2 (en) * | 2002-02-07 | 2005-01-18 | Jose Paul Moretto | Airliner irreversible-control anti-hijack system |
US7098810B2 (en) * | 2003-04-22 | 2006-08-29 | Honeywell International Inc. | Aircraft autorecovery systems and methods |
US20040215372A1 (en) * | 2003-04-22 | 2004-10-28 | Bateman Charles D. | Aircraft autorecovery systems and methods |
US7837143B2 (en) * | 2005-03-14 | 2010-11-23 | Matos Jeffrey A | Method and apparatus for disabling pilot control of a hijacked aircraft |
US7343239B2 (en) * | 2005-03-24 | 2008-03-11 | Hitachi, Ltd. | Program rewriting system and program rewriting method |
US7437225B1 (en) * | 2005-07-29 | 2008-10-14 | Rockwell Collins, Inc. | Flight management system |
Cited By (187)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7690603B2 (en) * | 2003-03-19 | 2010-04-06 | Airbus France | Method and device to assist in the piloting of an aircraft in a non-precision approach during a landing phase |
US20040245408A1 (en) * | 2003-03-19 | 2004-12-09 | Airbus France | Method and device to assist in the piloting of an aircraft in a non-precision approach during a landing phase |
US8521340B2 (en) * | 2005-12-07 | 2013-08-27 | Thales | Device and method of automated construction of emergency flight path for aircraft |
US20070219679A1 (en) * | 2006-03-14 | 2007-09-20 | Thales | Method of assisting in the navigation of an aircraft with an updating of the flight plan |
US8014907B2 (en) | 2006-03-14 | 2011-09-06 | Thales | Method of assisting in the navigation of an aircraft with an updating of the flight plan |
US7904213B2 (en) | 2006-03-14 | 2011-03-08 | Thales | Method of assisting in the navigation of an aircraft with an updating of the flight plan |
US20100121575A1 (en) * | 2006-04-04 | 2010-05-13 | Arinc Inc. | Systems and methods for aerial system collision avoidance |
US20080177432A1 (en) * | 2006-10-10 | 2008-07-24 | Thales | Method of forming a 3d safe emergency descent trajectory for aircraft and implementation device |
US7925394B2 (en) | 2006-10-10 | 2011-04-12 | Thales | Method of forming a 3D safe emergency descent trajectory for aircraft and implementation device |
US20120277986A1 (en) * | 2007-01-10 | 2012-11-01 | Honeywell International Inc. | Method and system to automatically generate a clearance request to deviate from a flight plan |
US8229659B2 (en) * | 2007-01-10 | 2012-07-24 | Honeywell International Inc. | Method and system to automatically generate a clearance request to deviate from a flight plan |
US20110257874A1 (en) * | 2007-01-10 | 2011-10-20 | Honeywell International Inc. | Method and system to automatically generate a clearance request to deviate from a flight plan |
US8423272B2 (en) * | 2007-01-10 | 2013-04-16 | Honeywell International Inc. | Method and system to automatically generate a clearance request to deviate from a flight plan |
US7979199B2 (en) * | 2007-01-10 | 2011-07-12 | Honeywell International Inc. | Method and system to automatically generate a clearance request to deviate from a flight plan |
US20080167885A1 (en) * | 2007-01-10 | 2008-07-10 | Honeywell International Inc. | Method and system to automatically generate a clearance request to deivate from a flight plan |
US8155803B2 (en) * | 2007-02-07 | 2012-04-10 | Airbus Operations Sas | Device and method for assisting in the management of an engine failure on an aircraft |
US20080243315A1 (en) * | 2007-02-07 | 2008-10-02 | Airbus France | Device and method for assisting in the management of an engine failure on an aircraft |
US20090125236A1 (en) * | 2007-03-13 | 2009-05-14 | Thales | Method for reducing nuisance alarms for anti-collision with obstacles on aircraft |
US7826971B2 (en) * | 2007-03-13 | 2010-11-02 | Thales | Method for reducing nuisance alarms for anti-collision with obstacles on aircraft |
US8126599B2 (en) | 2007-04-20 | 2012-02-28 | Thales | Method of calculating approach trajectory for aircraft |
US8024078B2 (en) | 2007-04-25 | 2011-09-20 | Thales | System for aiding the taxiing of an aircraft |
US8280564B2 (en) * | 2007-05-02 | 2012-10-02 | Thales | Method for optimizing the exit of an aircraft in a holding circuit |
US7681832B2 (en) | 2007-05-02 | 2010-03-23 | Honeywell International Inc. | Ducted fan air vehicle with deployable wings |
US20090005918A1 (en) * | 2007-05-02 | 2009-01-01 | Thales | Method for optimizing the exit of an aircraft in a holding circuit |
US20080294307A1 (en) * | 2007-05-22 | 2008-11-27 | The Boeing Company | Aircraft Guidance Using Localizer Capture Criteria for Rectilinear Displacement Data |
US7917254B2 (en) * | 2007-05-22 | 2011-03-29 | The Boeing Company | Aircraft guidance using localizer capture criteria for rectilinear displacement data |
US20100017053A1 (en) * | 2007-05-22 | 2010-01-21 | The Boeing Company | Consistent Localizer Captures |
US7941251B2 (en) * | 2007-05-22 | 2011-05-10 | The Boeing Company | Consistent localizer captures |
US20100017114A1 (en) * | 2007-05-24 | 2010-01-21 | Honeywell International Inc. | Flight Path Planning to Reduce Detection of an Unmanned Aerial Vehicle |
US7970532B2 (en) | 2007-05-24 | 2011-06-28 | Honeywell International Inc. | Flight path planning to reduce detection of an unmanned aerial vehicle |
US7737878B2 (en) * | 2007-07-09 | 2010-06-15 | Eads Deutschland Gmbh | Collision and conflict avoidance system for autonomous unmanned air vehicles (UAVs) |
US20090027253A1 (en) * | 2007-07-09 | 2009-01-29 | Eads Deutschland Gmbh | Collision and conflict avoidance system for autonomous unmanned air vehicles (UAVs) |
EP2023310A3 (en) * | 2007-07-26 | 2011-03-09 | The Boeing Company | Method and apparatus for managing instrument missed approaches |
US20090030564A1 (en) * | 2007-07-26 | 2009-01-29 | Mark Alan Peterson | Method and apparatus for managing instrument missed approaches |
EP2023310A2 (en) * | 2007-07-26 | 2009-02-11 | The Boeing Company | Method and apparatus for managing instrument missed approaches |
US8428794B2 (en) | 2007-07-26 | 2013-04-23 | The Boeing Company | Method and apparatus for managing instrument missed approaches |
US8335988B2 (en) * | 2007-10-02 | 2012-12-18 | Honeywell International Inc. | Method of producing graphically enhanced data communications |
US20090089693A1 (en) * | 2007-10-02 | 2009-04-02 | Honeywell International Inc. | Method of producing graphically enhanced data communications |
US20090157288A1 (en) * | 2007-12-12 | 2009-06-18 | The Boeing Company | Air Traffic Control Delay Factor |
US9257047B2 (en) * | 2007-12-12 | 2016-02-09 | The Boeing Company | Computation of new aircraft trajectory using time factor |
US8190310B2 (en) | 2008-02-08 | 2012-05-29 | Thales | Methods of optimizing the location of an aircraft on the ground and in the take-off and landing phases |
US8109711B2 (en) | 2008-07-18 | 2012-02-07 | Honeywell International Inc. | Tethered autonomous air vehicle with wind turbines |
US8615337B1 (en) * | 2008-09-25 | 2013-12-24 | Rockwell Collins, Inc. | System supporting flight operations under instrument meteorological conditions using precision course guidance |
US8032268B2 (en) * | 2008-09-29 | 2011-10-04 | Honeywell International Inc. | Methods and systems for indicating whether an aircraft is below a minimum altitude criterion for a sector |
US20100082186A1 (en) * | 2008-09-29 | 2010-04-01 | Honeywell International Inc. | Methods and systems for indicating whether an aircraft is below a minimum altitude criterion for a sector |
US8275499B2 (en) | 2008-10-17 | 2012-09-25 | Thales | Device for calculating a flight plan of an aircraft |
US8070092B2 (en) | 2008-10-31 | 2011-12-06 | Honeywell International Inc. | Noise-suppressing strut support system for an unmanned aerial vehicle |
US20100108809A1 (en) * | 2008-10-31 | 2010-05-06 | Honeywell International Inc. | Noise-suppressing strut support system for an unmanned aerial vehicle |
US20110001017A1 (en) * | 2008-12-08 | 2011-01-06 | Honeywell International Inc. | Uav ducted fan swept and lean stator design |
US8676481B2 (en) | 2008-12-23 | 2014-03-18 | Thales | Device for assisting in the choice of a diversion airport |
US20100161156A1 (en) * | 2008-12-23 | 2010-06-24 | Thales | Device for assisting in the choice of a diversion airport |
US8348190B2 (en) | 2009-01-26 | 2013-01-08 | Honeywell International Inc. | Ducted fan UAV control alternatives |
US20100187369A1 (en) * | 2009-01-26 | 2010-07-29 | Honeywell International Inc. | Ducted fan uav control alternatives |
US20100256839A1 (en) * | 2009-04-02 | 2010-10-07 | Honeywell International Inc. | Performing Corrective Action on Unmanned Aerial Vehicle Using One Axis of Three-Axis Magnetometer |
US8386095B2 (en) | 2009-04-02 | 2013-02-26 | Honeywell International Inc. | Performing corrective action on unmanned aerial vehicle using one axis of three-axis magnetometer |
US8244453B2 (en) | 2009-04-28 | 2012-08-14 | Thales | Method and device for adjusting the trajectory of an aircraft in a climb circuit |
US20100274419A1 (en) * | 2009-04-28 | 2010-10-28 | Thales | Method and Device for Adjusting the Trajectory of an Aircraft in a Climb Circuit |
WO2011024189A3 (en) * | 2009-07-20 | 2011-07-14 | Airbus Engineering Centre India | System and method for computing flight time from an equi- distance point to a reference point |
WO2011024189A2 (en) * | 2009-07-20 | 2011-03-03 | Airbus Engineering Centre India | System and method for computing flight time from an equi- distance point to a reference point |
US20110095530A1 (en) * | 2009-10-26 | 2011-04-28 | Honeywell International Inc. | Tethered aquatic device with water power turbine |
US20120215384A1 (en) * | 2009-10-30 | 2012-08-23 | Emerald Sky Technologies, LLC | Flight Control System with Dynamic Allocation of Functionality Between Flight Crew and Automation |
US20110231036A1 (en) * | 2010-03-22 | 2011-09-22 | Honeywell International Inc. | Aircraft communications radio tuning aid system and method |
US8340839B2 (en) | 2010-03-22 | 2012-12-25 | Honeywell International Inc. | Aircraft communications radio tuning aid system and method |
EP2498055B2 (en) † | 2010-09-14 | 2022-01-05 | The Boeing Company | Management System for Unmanned Aerial Vehicles |
EP2498055B1 (en) | 2010-09-14 | 2019-01-23 | The Boeing Company | Management System for Unmanned Aerial Vehicles |
US9004393B2 (en) | 2010-10-24 | 2015-04-14 | University Of Kansas | Supersonic hovering air vehicle |
US20120143482A1 (en) * | 2010-12-02 | 2012-06-07 | Honeywell International Inc. | Electronically file and fly unmanned aerial vehicle |
US20120221175A1 (en) * | 2011-02-28 | 2012-08-30 | The Boeing Company | Alternative communications for an air vehicle |
US9766337B2 (en) * | 2011-02-28 | 2017-09-19 | The Boeing Company | Alternative communications for an air vehicle |
US10249201B2 (en) * | 2011-02-28 | 2019-04-02 | The Boeing Company | Alternative communications for an air vehicle |
US20170154538A1 (en) * | 2011-02-28 | 2017-06-01 | The Boeing Company | Alternative communications for an air vehicle |
US20130066489A1 (en) * | 2011-09-08 | 2013-03-14 | Andrew Robert Hooks | Consistent Localizer Captures |
US8798820B2 (en) * | 2011-09-08 | 2014-08-05 | The Boeing Company | Consistent localizer captures |
US9052198B2 (en) | 2011-11-29 | 2015-06-09 | Airbus Operations (S.A.S.) | Interactive dialog device between an operator of an aircraft and a guidance system of said aircraft |
US8626429B2 (en) * | 2012-02-15 | 2014-01-07 | Hewlett-Packard Development Company, L.P. | Allocation of flight legs to dispatcher positions |
US20130211702A1 (en) * | 2012-02-15 | 2013-08-15 | Cipriano A. Santos | Allocation of flight legs to dispatcher positions |
US20140032103A1 (en) * | 2012-07-26 | 2014-01-30 | Ge Aviation Systems Llc | Method of displaying a flight plan |
US8843303B1 (en) * | 2012-12-17 | 2014-09-23 | Rockwell Collins, Inc. | Risk-aware contingency flight re-planner system and related method |
US11699351B2 (en) | 2012-12-28 | 2023-07-11 | Otto Aero Company | Flight assistant |
US11935420B1 (en) * | 2012-12-28 | 2024-03-19 | Sean Patrick Suiter | Flight assistant |
US11551564B2 (en) * | 2012-12-28 | 2023-01-10 | Otto Aero Company | Aircraft with landing system |
US9174725B2 (en) | 2013-01-11 | 2015-11-03 | Airbus Operations (S.A.S.) | Systems for tasks guidance of operations management in an aircraft cockpit |
US8798815B1 (en) | 2013-03-13 | 2014-08-05 | Honeywell International Inc. | System and method alerting an aircrew of threshold altitudes |
US9280904B2 (en) | 2013-03-15 | 2016-03-08 | Airbus Operations (S.A.S.) | Methods, systems and computer readable media for arming aircraft runway approach guidance modes |
US20140288730A1 (en) * | 2013-03-19 | 2014-09-25 | The Boeing Company | Method of Flying an Unmanned Aerial Vehicle |
JP2014181034A (en) * | 2013-03-19 | 2014-09-29 | Boeing Co | Method of flying unmanned aerial vehicle |
US9359067B2 (en) * | 2013-03-19 | 2016-06-07 | The Boeing Company | Method of flying an unmanned aerial vehicle |
US9567099B2 (en) * | 2013-04-11 | 2017-02-14 | Airbus Operations (S.A.S.) | Aircraft flight management devices, systems, computer readable media and related methods |
US20140309821A1 (en) * | 2013-04-11 | 2014-10-16 | Airbus Operations SAS (France) | Aircraft flight management devices, systems, computer readable media and related methods |
US9199724B2 (en) | 2013-05-15 | 2015-12-01 | Honeywell International Inc. | System and method for performing an aircraft automatic emergency descent |
US9368036B2 (en) * | 2013-06-28 | 2016-06-14 | Thales | Method and device for calculating a flight plan of an aircraft in a runway approach phase |
US20150005992A1 (en) * | 2013-06-28 | 2015-01-01 | Thales | Method and device for calculating a flight plan of an aircraft in a runway approach phase |
US20150266591A1 (en) * | 2013-07-10 | 2015-09-24 | Airbus Helicopters | Method and a device for issuing terrain avoidance warnings for a rotary wing aircraft |
US9199744B2 (en) * | 2013-07-10 | 2015-12-01 | Airbus Helicopters | Method and a device for issuing terrain avoidance warnings for a rotary wing aircraft |
US11657721B1 (en) * | 2013-08-26 | 2023-05-23 | Otto Aero Company | Aircraft with flight assistant |
US20160299231A1 (en) * | 2013-11-11 | 2016-10-13 | Airbus Defence Ang Space Gmbh | Aircraft navigation system and method of navigating an aircraft |
US9753143B2 (en) * | 2013-11-11 | 2017-09-05 | Airbus Defence and Space GmbH | Aircraft navigation system and method of navigating an aircraft |
US10250821B2 (en) * | 2013-11-27 | 2019-04-02 | Honeywell International Inc. | Generating a three-dimensional model of an industrial plant using an unmanned aerial vehicle |
US20150145954A1 (en) * | 2013-11-27 | 2015-05-28 | Honeywell International Inc. | Generating a three-dimensional model of an industrial plant using an unmanned aerial vehicle |
US10824170B2 (en) | 2013-11-27 | 2020-11-03 | Aurora Flight Sciences Corporation | Autonomous cargo delivery system |
US20170076612A1 (en) * | 2014-04-25 | 2017-03-16 | Sony Corporation | Information processing device, information processing method, program, and imaging system |
US9865172B2 (en) * | 2014-04-25 | 2018-01-09 | Sony Corporation | Information processing device, information processing method, program, and imaging system |
US20150346986A1 (en) * | 2014-05-27 | 2015-12-03 | Thales | Device and method for generating at least one computer file for producing a graphic interface of an electronic equipment, and related computer program product |
US9996238B2 (en) * | 2014-05-27 | 2018-06-12 | Thales | Device and method for generating at least one computer file for producing a graphic interface of an electronic equipment, and related computer program product |
US10339816B2 (en) * | 2014-06-27 | 2019-07-02 | The Boeing Company | Automatic aircraft monitoring and operator preferred rerouting system and method |
US20150379875A1 (en) * | 2014-06-27 | 2015-12-31 | The Boeing Company | Automatic aircraft monitoring and operator preferred rerouting system and method |
US9466218B2 (en) | 2014-07-14 | 2016-10-11 | John A. Jarrell | Unmanned aerial vehicle communication, monitoring, and traffic management |
US9087451B1 (en) | 2014-07-14 | 2015-07-21 | John A. Jarrell | Unmanned aerial vehicle communication, monitoring, and traffic management |
US9576493B2 (en) | 2014-07-14 | 2017-02-21 | John A. Jarrell | Unmanned aerial vehicle communication, monitoring, and traffic management |
US9691285B2 (en) | 2014-07-14 | 2017-06-27 | John A. Jarrell | Unmanned aerial vehicle communication, monitoring, and traffic management |
CN104260896A (en) * | 2014-09-01 | 2015-01-07 | 陈宜中 | Method for passengers to participate in alarming when passenger plane meets with hijacking |
US9424755B2 (en) | 2014-09-30 | 2016-08-23 | The Boeing Company | Flight analogous and projection system |
US9508264B2 (en) * | 2014-09-30 | 2016-11-29 | Elwha Llc | System and method for management of airspace for unmanned aircraft |
US9754496B2 (en) * | 2014-09-30 | 2017-09-05 | Elwha Llc | System and method for management of airspace for unmanned aircraft |
US9472106B2 (en) | 2014-09-30 | 2016-10-18 | The Boeing Company | Automated flight object procedure selection system |
US9443434B2 (en) | 2014-09-30 | 2016-09-13 | The Boeing Company | Flight path discontinuities |
US9697737B2 (en) | 2014-09-30 | 2017-07-04 | The Boeing Company | Automatic real-time flight plan updates |
US10134291B2 (en) | 2014-09-30 | 2018-11-20 | Elwha Llc | System and method for management of airspace for unmanned aircraft |
US10121384B2 (en) * | 2014-09-30 | 2018-11-06 | The Boeing Company | Aircraft performance predictions |
US9530320B2 (en) | 2014-09-30 | 2016-12-27 | The Boeing Company | Flight object communications system |
US10026324B2 (en) | 2014-11-04 | 2018-07-17 | Honeywell International Inc. | Systems and methods for enhanced adoptive validation of ATC clearance requests |
US9902491B2 (en) | 2014-12-04 | 2018-02-27 | Elwha Llc | Reconfigurable unmanned aircraft system |
US9878786B2 (en) | 2014-12-04 | 2018-01-30 | Elwha Llc | System and method for operation and management of reconfigurable unmanned aircraft |
US9919797B2 (en) | 2014-12-04 | 2018-03-20 | Elwha Llc | System and method for operation and management of reconfigurable unmanned aircraft |
US9666082B2 (en) * | 2014-12-23 | 2017-05-30 | Thales | Method and system for guidance of an aircraft |
US20160180716A1 (en) * | 2014-12-23 | 2016-06-23 | Thales | Method and system for guidance of an aircraft |
US10144505B2 (en) * | 2015-05-18 | 2018-12-04 | The Boeing Company | Aircraft flight control using a required time of arrival index |
US20160343257A1 (en) * | 2015-05-18 | 2016-11-24 | The Boeing Company | Aircraft flight control using a required time of arrival index |
US9878787B2 (en) | 2015-07-15 | 2018-01-30 | Elwha Llc | System and method for operating unmanned aircraft |
US10175699B2 (en) * | 2015-07-16 | 2019-01-08 | Safran Electronics And Defense | Method for automatically assisting with the landing of an aircraft |
US10814978B2 (en) | 2015-07-16 | 2020-10-27 | Physio-Control, Inc. | Unmanned aerial vehicles in medical applications |
US9994315B2 (en) * | 2015-07-16 | 2018-06-12 | Physio-Control, Inc. | Unmanned aerial vehicles in medical applications |
US10341011B2 (en) * | 2015-08-13 | 2019-07-02 | Bae Systems Plc | Apparatus and method for communications management |
US20170197710A1 (en) * | 2015-09-07 | 2017-07-13 | Tao Ma | Passenger transport systems based on pilotless vertical takeoff and landing (vtol) aircraft |
US10319246B2 (en) | 2015-09-29 | 2019-06-11 | Airbus Defence and Space GmbH | Unmanned aerial vehicle and method for safely landing an unmanned aerial vehicle |
EP3151080A1 (en) * | 2015-09-29 | 2017-04-05 | Airbus Defence and Space GmbH | Unmanned aircraft and method for secure landing of an unmanned aircraft |
EP3163394A1 (en) * | 2015-10-30 | 2017-05-03 | Xiaomi Inc. | Method and device for controlling an unmanned aerial vehicle |
US20220172630A1 (en) * | 2016-02-29 | 2022-06-02 | Garmin International, Inc. | Emergency autoland system |
US11282399B2 (en) * | 2016-02-29 | 2022-03-22 | Garmin International, Inc. | Emergency autoland system |
US11862029B2 (en) * | 2016-02-29 | 2024-01-02 | Garmin International, Inc. | Emergency autoland system |
US10228694B2 (en) * | 2016-03-04 | 2019-03-12 | Animusoft Corporation | Drone and robot control systems and methods |
US11217106B2 (en) | 2016-03-08 | 2022-01-04 | International Business Machines Corporation | Drone air traffic control and flight plan management |
US10540900B2 (en) * | 2016-03-08 | 2020-01-21 | International Business Machines Corporation | Drone air traffic control and flight plan management |
US10417917B2 (en) | 2016-03-08 | 2019-09-17 | International Business Machines Corporation | Drone management data structure |
US11183072B2 (en) | 2016-03-08 | 2021-11-23 | Nec Corporation | Drone carrier |
US11151885B2 (en) | 2016-03-08 | 2021-10-19 | International Business Machines Corporation | Drone management data structure |
US10922983B2 (en) | 2016-03-08 | 2021-02-16 | International Business Machines Corporation | Programming language for execution by drone |
US10899444B2 (en) | 2016-03-08 | 2021-01-26 | International Business Machines Corporation | Drone receiver |
US10529221B2 (en) | 2016-04-19 | 2020-01-07 | Navio International, Inc. | Modular approach for smart and customizable security solutions and other applications for a smart city |
US10950118B2 (en) | 2016-04-19 | 2021-03-16 | Navio International, Inc. | Modular sensing systems and methods |
US11790760B2 (en) | 2016-04-19 | 2023-10-17 | Navio International, Inc. | Modular sensing systems and methods |
US10789853B2 (en) | 2016-06-10 | 2020-09-29 | ETAK Systems, LLC | Drone collision avoidance via air traffic control over wireless networks |
US11436929B2 (en) | 2016-06-10 | 2022-09-06 | Metal Raptor, Llc | Passenger drone switchover between wireless networks |
US10074284B1 (en) * | 2016-06-10 | 2018-09-11 | ETAK Systems, LLC | Emergency shutdown and landing for unmanned aerial vehicles with air traffic control systems |
US11727813B2 (en) | 2016-06-10 | 2023-08-15 | Metal Raptor, Llc | Systems and methods for air traffic control for passenger drones |
US11710414B2 (en) | 2016-06-10 | 2023-07-25 | Metal Raptor, Llc | Flying lane management systems and methods for passenger drones |
US11670179B2 (en) | 2016-06-10 | 2023-06-06 | Metal Raptor, Llc | Managing detected obstructions in air traffic control systems for passenger drones |
US10720066B2 (en) | 2016-06-10 | 2020-07-21 | ETAK Systems, LLC | Flying lane management with lateral separations between drones |
US11670180B2 (en) | 2016-06-10 | 2023-06-06 | Metal Raptor, Llc | Obstruction detection in air traffic control systems for passenger drones |
US11488483B2 (en) | 2016-06-10 | 2022-11-01 | Metal Raptor, Llc | Passenger drone collision avoidance via air traffic control over wireless network |
US11250709B2 (en) | 2016-06-10 | 2022-02-15 | Metal Raptor, Llc | Drone air traffic control incorporating weather updates |
US11263909B2 (en) | 2016-06-10 | 2022-03-01 | Metal Raptor, Llc | Air traffic control of passenger drones concurrently using a plurality of wireless networks |
US11468778B2 (en) | 2016-06-10 | 2022-10-11 | Metal Raptor, Llc | Emergency shutdown and landing for passenger drones and unmanned aerial vehicles with air traffic control |
US11328613B2 (en) | 2016-06-10 | 2022-05-10 | Metal Raptor, Llc | Waypoint directory in air traffic control systems for passenger drones and unmanned aerial vehicles |
US11341858B2 (en) | 2016-06-10 | 2022-05-24 | Metal Raptor, Llc | Managing dynamic obstructions in air traffic control systems for passenger drones and unmanned aerial vehicles |
US11403956B2 (en) | 2016-06-10 | 2022-08-02 | Metal Raptor, Llc | Air traffic control monitoring systems and methods for passenger drones |
US11355020B2 (en) | 2016-06-10 | 2022-06-07 | Metal Raptor, Llc | Drone air traffic control over wireless networks for package pickup and delivery |
US10284525B2 (en) * | 2016-07-11 | 2019-05-07 | Honeywell Lntemational Inc. | Cross-domain data-gate for secure transmission of data over publicly shared datalinks |
US10020872B2 (en) * | 2016-10-11 | 2018-07-10 | T-Mobile Usa, Inc. | UAV for cellular communication |
US9866313B1 (en) | 2016-12-14 | 2018-01-09 | T-Mobile Usa, Inc. | UAV cellular communication service delivery |
US10019905B1 (en) * | 2017-03-24 | 2018-07-10 | The Boeing Company | Aircraft holding pattern analysis system and method |
US10689107B2 (en) | 2017-04-25 | 2020-06-23 | International Business Machines Corporation | Drone-based smoke detector |
US10423831B2 (en) | 2017-09-15 | 2019-09-24 | Honeywell International Inc. | Unmanned aerial vehicle based expansion joint failure detection system |
US11138892B2 (en) | 2017-12-19 | 2021-10-05 | Honeywell International Inc. | TCAS coupled FMS |
CN109444806A (en) * | 2018-10-15 | 2019-03-08 | 中海油信息科技有限公司 | Offshore drilling platforms helicopter navigation frequency multiplex system and method |
DE102018218715A1 (en) * | 2018-10-31 | 2020-04-30 | Airbus Defence and Space GmbH | Method for operating an at least temporarily unmanned aircraft and such an aircraft |
US10621661B1 (en) | 2018-11-09 | 2020-04-14 | Capital One Services, Llc | Systems and methods for automatic route re-determination for an unmanned aerial vehicle |
US10319030B1 (en) | 2018-11-09 | 2019-06-11 | Capital One Services, Llc | Systems and methods for automatic route re-determination for an unmanned aerial vehicle |
CN111522354A (en) * | 2019-02-01 | 2020-08-11 | 中强光电股份有限公司 | Unmanned aerial vehicle and failure safety method thereof |
CN111552310A (en) * | 2019-02-08 | 2020-08-18 | 沃科波特有限公司 | Aircraft and motion planning method and system thereof |
EP3799010A1 (en) * | 2019-09-25 | 2021-03-31 | Honeywell International Inc. | Complete loss of engine thrust aircraft guidance to runway system and method |
US11959773B2 (en) | 2019-09-25 | 2024-04-16 | Honeywell International Inc. | All-engine-out aircraft guidance to runway |
US20230129329A1 (en) * | 2021-10-25 | 2023-04-27 | Aurora Flight Sciences Coporation, A Subsidiary Of The Boing Company | Guidance modes for an unmanned aerial vehicle |
EP4276792A3 (en) * | 2022-04-19 | 2024-02-28 | Rockwell Collins, Inc. | Autonomous air traffic control interaction |
US11722462B1 (en) * | 2022-04-28 | 2023-08-08 | Beta Air, Llc | Systems and methods for encrypted flight plan communications |
US11573579B1 (en) * | 2022-05-23 | 2023-02-07 | Zhuhai Xiangyi Aviation Technology Company Ltd. | Method, system, and device for planning path for forced landing of aircraft based on image recognition |
US11710412B1 (en) * | 2022-09-23 | 2023-07-25 | Sichuan University | Method and device for flight path planning considering both the flight trajectory and the visual images from air traffic control systems for air traffic controllers |
Also Published As
Publication number | Publication date |
---|---|
US8521340B2 (en) | 2013-08-27 |
EP1796060B1 (en) | 2010-02-10 |
FR2894368A1 (en) | 2007-06-08 |
DE602006012157D1 (en) | 2010-03-25 |
FR2894368B1 (en) | 2008-01-25 |
CA2569947A1 (en) | 2007-06-07 |
EP1796060A1 (en) | 2007-06-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8521340B2 (en) | Device and method of automated construction of emergency flight path for aircraft | |
RU2712716C2 (en) | Unmanned aerial vehicle and method of safe landing of unmanned aerial vehicle | |
US7925394B2 (en) | Method of forming a 3D safe emergency descent trajectory for aircraft and implementation device | |
CN105425813B (en) | Method for real-time calculation of planning tracks, combined tasks and system for managing such tracks | |
US7412324B1 (en) | Flight management system with precision merging | |
US9709991B2 (en) | Management of the energy in an approach trajectory | |
US20220189316A1 (en) | Unmanned aircraft control using ground control station | |
US8027783B2 (en) | Device for guiding an aircraft along a flight trajectory | |
Nikoleris et al. | Autonomous system for air traffic control in terminal airspace | |
EP2333743B1 (en) | Multiple transition RNP approach procedure | |
US20160180716A1 (en) | Method and system for guidance of an aircraft | |
WO2023059366A1 (en) | Autonomous aircraft separation system and method | |
Di Vito et al. | Enabling SAT single pilot operations: tactical separation system design advancements in the COAST project | |
Bulusu et al. | Analysis of interactions between Urban Air Mobility (UAM) operations and current air traffic in urban areas: Traffic alert and Collision Avoidance System (TCAS) study for UAM Operations | |
US11735055B2 (en) | Method and system for controlling interval management of an aircraft | |
US11822352B2 (en) | Engine out go around vertical clearance system and method | |
Prats et al. | Departure and approach procedures for unammed aircraft systems in a visual-flight-rule environment | |
Ramasamy | Next generation flight management systems for manned and unmanned aircraft operations-automated separation assurance and collision avoidance functionalities | |
Chatterji et al. | Functional Allocation Approach for Separation Assurance for Remotely Piloted Aircraft | |
CN112817323A (en) | Dynamic flight mode control method for land-based cruise process | |
Gonzaga Lopez | Design of rotorcraft performance-based navigation routes and procedures: current challenges and prospects | |
Weber et al. | Avionics to enable UAS integration into the NextGen ATS | |
Perrottet | Enabling unrestricted UAS airspace access: Performance based navigation | |
Wing et al. | Airborne tactical intent-based conflict resolution capability | |
DK2422333T3 (en) | Position imaging system and for air traffic intensity simulation |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: THALES, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:COULMEAU, FRANNCOIS;REEL/FRAME:018598/0022 Effective date: 20061205 |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20210827 |