Flight Planning is the most common use of LMFS the Leidos Web Services. The current offering provides the following capabilities:
- Filing
- Amending
- Activating
- Cancelling
- Closing
- Retrieve
Filing
LMFS Our Leidos Web Services offering allows developers to file the FAA domestic flight plan form or the ICAO flight plan form for IFR and VFR flight plans. We also provide support for flights leaving and arriving in the United States (International to International flights are not supported). Some aspects to know about our system that will help you get a better understanding of how things work and put you in a better position to answer questions from your users:
- VFR Flight Plans: VFR Flight Plans remain within the LMFS Leidos system throughout the duration of a flight. Once you file a VFR flight plan, it can be amended until or cancelled or for up to 2 hours past the estimated time of departure (ETD). It can be activated within 30 minutes of the current time (before or after). After activation, the flight plan can be amended until the flight plan is closed. The flight plan must be closed within 30 minutes after the estimated time of arrival (ETA). Note: LMFS Leidos offers an advanced service that sends a notification to a pilot to close their flight plan before it is overdue - one reason to considered credentialed filing. You may also consider such a reminder in your own application.
- IFR Flight Plans: IFR Flight Plans are routed to the appropriate ARTCC for the flight to be managed by ATC. At 3 The flight plan is transmitted to an Air Route Traffic Control Center (ARTCC) at 22.5 hours prior to ETD ( or immediately if filed within this window), it is transmitted to ATC. When the ETD is in less than 22.5 hours. When the flight plan is ROGERED by ATC, the flight plan will not be accessible via web services after ETD. A flight plan can be amended or cancelled up to 30 46 minutes prior to ETD. After that, the pilot will need to contact the requisite ATC center to manage the flight plan.
- For more detailed information, see:
Status of a flight plan can be pulled via web services through a retrieveFlightPlan request or the notifications can be pushed to you via a registered webhook
An example of a flight plan and the expected response:
Code Block | ||||
---|---|---|---|---|
| ||||
$ /usr/bin/curl -k -A "Mozilla/5.0" -i --header "Authorization: Basic bWVAbGV0bWVpbi5jb206TXlQYXNzdzByZCE=" --data "type=DOMESTIC&webUserName=me%40letmein.com&flightRules=VFR&aircraftIdentifier=TTTDEMO&departure=HOU&destination=MIA&departureInstant=2015-03-04T14:48:00.0&flightDuration=PT1H30M&route=LEV%20Q102%20CYY%20SSCOT&altDestination1=LAX&altDestination2=SEA&aircraftType=P28A&numberOfAircraft=3&heavyWakeTurbulence=true&aircraftEquipment=G&remarks=This%20is%20a%20domestic%20flight%20plan%20test&speedKnots=100&altitudeFL=35&fuelOnBoard=PT20H0M&pilotData=PILOT%20INFO&peopleOnBoard=1&aircraftColor=W" "httphttps://[Operational or Test Environment URL]/rest/FP/file" -v {"versionStamp":"20150304024814280","flightIdentifier":"298351728_447141_1053","returnCodedMessage":[],"returnMessage":[],"returnStatus":true} |
Important items to note in the response:
- The versionStamp is the version of the flight plan that is retained in our system. Whenever you do anything to modify the flight plan, you need to reference the latest version of the time stamp.
- The flightIdentifier is a unique identifier that is associated with every flight plan that is created in the system. It is used with other web service calls that fetch data based on a specific flight plan such as retrieveFlightPlan, amendFlightPlan, cancelFlightPlan, and amendFlightPlancloseFlightPlan. This value does not change. You should retain this information on your side so you have a reference to it in the future, particularly if you are using anonymous filing.
...
Code Block | ||||
---|---|---|---|---|
| ||||
$ /usr/bin/curl -k -A "Mozilla/5.0" -i --header "Authorization: Basic bWVAbGV0bWVpbi5jb206TXlQYXNzdzByZCE=" --data "type=DOMESTIC&versionStamp=20150304024814280&webUserName=me%40letmein.com&flightRules=IFR&aircraftIdentifier=TTTDEMO&departure=HOU&destination=MIA&departureInstant=2015-03-04T14:48:00.0&flightDuration=PT1H20M&route=&altDestination1=&altDestination2=&aircraftType=L18&numberOfAircraft=&aircraftEquipment=X&remarks=&speedKnots=150&altitudeFL=45&fuelOnBoard=PT21H0M&pilotData=JOE%20COOL&peopleOnBoard=2&aircraftColor=B" "httphttps://[Operational or Test Environment URL]/rest/FP/298351728_447141_1053/amend" -v {"versionStamp":"20150304024817490","returnCodedMessage":[],"returnMessage":[],"returnStatus":true} |
...
Code Block | ||||
---|---|---|---|---|
| ||||
$ /usr/bin/curl -k -A "Mozilla/5.0" -i --header "Authorization: Basic bWVAbGV0bWVpbi5jb206TXlQYXNzdzByZCE=" --data "&actualDepartureInstant=2015-03-04T15:03:00.0&versionStamp=20150304024817490&includeCodedMessages=true""httphttps://[Operational or Test Environment URL]/rest/FP/298351728_447141_1053/activate" -v {"versionStamp":"20150304030332170","returnCodedMessage":[],"returnMessage":[],"returnStatus":true} |
...
Code Block | ||||
---|---|---|---|---|
| ||||
$ /usr/bin/curl -k -A "Mozilla/5.0" -i --header "Authorization: Basic bWVAbGV0bWVpbi5jb206TXlQYXNzdzByZCE=" --data "includeCodedMessages=true" "httphttps://[Operational or Test Environment URL]/rest/FP/298351728_447141_1053/close" -v {"returnCodedMessage":[],"returnMessage":[],"returnStatus":true} |
...