The present invention relates to systems and methods for providing candidate flight plan data to users.
It is known in the prior art to allow a user to enter flight plan information and file a flight plan via the Internet with an aviation authority, such as the Federal Aviation Administration (FAA). When a pilot files a flight plan with the FAA, the FAA acknowledges that it has received it and the flight plan is considered “accepted”. However, use of this procedure does not require the FAA to allow that flight plan to be followed. Depending on air traffic and weather conditions, the FAA may modify the flight plan route. Typically before takeoff, the pilot will contact the FAA and find out what route was cleared or “activated”.
It is also known in prior art to extract and store flight plan data available from air traffic data, and to provide such flight plan data to a user. It also known to store flight plan data for previous flights between a departure airport and a destination airport and provide this flight plan data to a user. Additionally, it is known to extract from this stored flight plan data that which is associated with a selected type of aircraft.
In a first embodiment of the invention there is provided a method for providing, to a user, flight plan data for an air trip of interest from a first location to a second location, the method includes: extracting and storing flight plan data from live air traffic data collected over a period of a plurality of days, the flight plan data stored in a flight plan data base, accessible by a starting location and an ending location and including at least one of as-filed, as-cleared and as-flown flight plans, wherein at least one of time data and weather data pertinent to flight plan data in the flight plan database is also stored; accessing and abstracting, from the flight plan data base, flight plan data pertinent to the trip of interest; and providing the abstracted flight plan data to the user.
The method optionally includes storing both time data and weather data pertinent to flight plan data in the flight plan database.
The method optionally includes storing time data pertinent to flight plan data in the flight plan database.
The method optionally includes storing weather data pertinent to flight plan data in the flight plan database.
In a further related embodiment of the invention, there is provided a method of associating at least one of anticipated weather conditions and scheduled time of day for the air trip of interest and using such association in accessing flight plan data from the flight plan data base.
The method optionally includes associating both anticipated weather conditions and scheduled time of day for the air trip of interest and using such association in accessing flight plan data from the flight plan data base.
The method optionally includes associating scheduled time of day for the air trip of interest and using such association in accessing flight plan data from the flight plan data base.
The method optionally includes associating anticipated weather conditions for the air trip of interest and using such association in accessing flight plan data from the flight plan data base.
The method optionally includes providing the abstracted flight plan data to the user using a wireless communications network. The wireless communications network may be in communication with a wide area network and receive the abstracted flight plan data over the wide area network. The wide area network may be the internet. The wireless communications network may be a data link in a mobile telephone system. The abstracted flight plan data is communicated to a wireless transceiver of the user that is in communication with the wireless communications network.
In another related embodiment the method optionally includes providing the abstracted flight plan data to the user communicating such data over a wide area network. The wide area network may be the internet.
In a further related embodiment, when the flight plan data pertinent to the trip of interest relates to a plurality of accessed routes, the method includes: ranking each of the accessed routes according to an estimated probability that such route would be selected as part of a cleared flight plan for the trip of interest, and providing, to the user, information based on such ranking.
The method optionally includes associating at least one of anticipated weather conditions and scheduled time of day for the air trip of interest and using such association in ranking each of the accessed routes.
The method optionally includes associating both anticipated weather conditions and scheduled time of day for the air trip of interest and using such association in ranking each of the accessed routes.
The method optionally includes associating scheduled time of day for the air trip of interest and using such association in ranking each of the accessed routes.
The method optionally includes associating anticipated weather conditions for the air trip of interest and using such association in ranking each of the accessed routes.
The method optionally includes associating aircraft type for the air trip of interest and using such association in ranking each of the accessed routes.
The method optionally includes associating at least one of altitude, speed information, and time en route, for the trip of interest and using such association in ranking each of the accessed routes.
In a further related embodiment there is a method of providing the abstracted flight plan data to the user before the user has obtained regulatory clearance to make the trip of interest and to facilitate proposing by the user of a route that is likely to obtain such clearance.
In a further related embodiment there is a method for providing, to a user, flight plan data for an air trip, for which the flight has not begun, from a departure airport to a destination airport, the method comprising: extracting flight plan data, from live air traffic data, pertinent to the trip; providing flight plan data, derived from the extracted data, over a data link in a mobile telephone system to a wireless transceiver of a user. The wireless transceiver of the user may be in communication with a GPS system of the user, such GPS system being updatable with the routed flight plan data.
In a further related embodiment there is a method for providing, to a user, flight plan data for an air trip of interest from a first location to a second location, the method comprising: extracting and storing flight plan data from live air traffic data collected over a period of a plurality of days, the flight plan data stored in a flight plan data base, accessible by a starting location and an ending location and including at least one of as-filed, as-cleared and as-flown flight plans; accessing, from the flight plan data base, a plurality of routes pertinent to the trip of interest; ranking each of the accessed routes according to an estimated probability that such route would be selected as part of a cleared flight plan for the trip of interest; and providing, to the user, information based on such ranking.
Such ranking may be provided to the user before the user has obtained regulatory clearance to make the trip of interest and to facilitate proposing by the user of a route that is likely to obtain such clearance.
Optionally the method may include ranking each of the accessed routes by considering time of day of the trip of interest in relation to time of day associated with each of the accessed routes. This may optionally include ranking each of the accessed routes by considering day of the week of the trip of interest, and presence of any holiday on such day, in relation to day of the week, and the presence of any holiday on such day, associated with each of the accessed routes.
In a further related embodiment there is a method wherein ranking each of the accessed routes includes considering weather conditions expected for the trip of interest in relation to the weather conditions associated with each of the accessed routes.
In a further related embodiment there is a method wherein ranking each of the accessed routes includes considering aircraft type associated with the trip of interest in relation to aircraft type associated with each of the accessed routes.
The method optionally includes providing information based on such ranking to the user using a wireless communications network. The wireless communications network may be in communication with a wide area network and receive the abstracted flight plan data over the wide area network. The wide area network may be the internet. The wireless communications network may be a data link in a mobile telephone system. The abstracted flight plan data is communicated to a wireless transceiver of the user that is in communication with the wireless communications network.
In another related embodiment the method optionally includes providing the abstracted flight plan data to the user communicating such data over a wide area network. The wide area network may be the internet.
The foregoing features of the invention will be more readily understood by reference to the following detailed description, taken with reference to the accompanying drawings, in which:
Definitions. As used in this description and the accompanying claims, the following terms shall have the meanings indicated, unless the context otherwise requires:
Each flight plan would typically include: the airline and flight identifier or tail number, aircraft type, altitude, speed, status of flight, departure and arrival airports, departure and arrival times, a flight plan route described by fixes and airways. Also, data can be derived from the flight plan data, for example, time en route and distance. This information can be stored with the flight plan data. For the purposes of this description, extracted flight plan data shall include the extracted flight plan data and any data derived from the extracted flight plan data, such as the time en route or distance.
In one embodiment, live air traffic data is received from the Federal Aviation Administration (FAA). The FAA provides as-cleared and as-flown flight plan data in its Aircraft Situation Display for Industry (ASDI) data.
In accordance with process 22 of
Again referring to process 22 of
In these embodiments the flight plan data, and optionally the weather data, are collected 20 over a period of a plurality of days, for example, three years.
The Database Manager 24 of
The Database Manager associates the anticipated weather conditions and scheduled time of day for the air trip of interest and uses such association in accessing flight plan data from the flight plan database. In a further embodiment, the Database Manager associates both the anticipated weather conditions and scheduled time of day for the air trip of interest and uses such association in accessing flight plan data from the flight plan database. In yet a further embodiment, when the Database Manager associates a plurality of flight plan data pertinent to the trip of interest, the Database Manager ranks each of the accessed routes according to an estimated probability that such route would be selected as part of a cleared flight plan for the trip of interest.
As an example of such an embodiment, the user selects, on the web page, a departure airport of Teterboro (TEB), New Jersey, and an arrival airport of West Palm Beach (PBI), Florida, and a departure time of 11:30 AM (EST). This information is passed from the User Interface Program to the Database Manager. The Database Manager then retrieves from the Flight Plan Database all flights routed between TEB and PBI. For each route retrieved, the Database Manager determines if the weather conditions en route, say at specific fixes or waypoints, match or perhaps are somewhat worse than the anticipated weather en route. The Database Manager formats and ranks the results, showing the most frequently cleared flight plan through to the least frequently cleared flight plan.
As shown in
In another embodiment, the Database Manager 24 optionally associates aircraft type for the air trip of interest and uses such association in ranking each of the accessed routes. Additionally the Database Manager may associate at least one of altitude, speed information, and time en route, for the trip of interest and uses such association in ranking each of the accessed routes. For example, the user could select a time en route and an aircraft type as criteria for ranking each of the accessed routes.
In a further embodiment the Flight Plan Manager receives and extracts flight plan data, but not weather data. As previously shown in
Also as previously shown in
In a further related embodiment the Database Manager 24 provides to the user abstracted flight plan data that contains a plurality of accessed routes ranked according to an estimated probability that such route would be selected as part of a cleared flight plan for the trip of interest. This flight plan data is provided to the user before the user has obtained regulatory clearance to make the trip of interest and facilitates proposing by the user of a route that is likely to obtain such clearance. The user may then select the best flight plan, say by clicking on it, and the User Interface 12 passes the flight plan onto a flight plan filing system.
In a further embodiment the flight plan data may be communicated to the user via a wireless communications network. The wireless communications network may be in communications with a wide area network and receive the flight plan data over the wide area network. The wide area network may be an internet.
In a further embodiment the wireless communications network includes a data link in a mobile telephone system and providing the abstracted flight plan data to the user includes providing such data to a wireless transceiver of the user that is in communication with the wireless communications network.
This application claims priority to U.S. Provisional Patent Application Ser. No. 60/681,181, filed May 13, 2005, and which is hereby incorporated by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
4774670 | Palmieri | Sep 1988 | A |
5051910 | Liden | Sep 1991 | A |
5265023 | Sokkappa | Nov 1993 | A |
6134500 | Tang et al. | Oct 2000 | A |
6199008 | Aratow et al. | Mar 2001 | B1 |
6278965 | Glass et al. | Aug 2001 | B1 |
6922631 | Dwyer et al. | Jul 2005 | B1 |
7363319 | Cappellini | Apr 2008 | B2 |
7546206 | Miller et al. | Jun 2009 | B1 |
20030055689 | Block et al. | Mar 2003 | A1 |
20030109266 | Rafiah et al. | Jun 2003 | A1 |
20040030593 | Webster et al. | Feb 2004 | A1 |
20040039617 | Maycotte et al. | Feb 2004 | A1 |
20040183695 | Ruokangas et al. | Sep 2004 | A1 |
20050080551 | Ledingham et al. | Apr 2005 | A1 |
20050096946 | Janakiraman et al. | May 2005 | A1 |
20050178903 | Boorman et al. | Aug 2005 | A1 |
20050187812 | Boedi et al. | Aug 2005 | A1 |
20050220278 | Zirngibl et al. | Oct 2005 | A1 |
20050288831 | Lusardi et al. | Dec 2005 | A1 |
20060089760 | Love et al. | Apr 2006 | A1 |
20060106768 | van Deursen | May 2006 | A1 |
Number | Date | Country |
---|---|---|
2 327 517 | Jan 1999 | GB |
Number | Date | Country | |
---|---|---|---|
20060259234 A1 | Nov 2006 | US |
Number | Date | Country | |
---|---|---|---|
60681181 | May 2005 | US |