BoldPilot

BoldPilot

There are old pilots... there are bold pilots...

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
cocc:flight_plan [2025/05/20 17:32] – created zackcocc:flight_plan [2025/06/07 22:23] (current) – [EET] zack
Line 1: Line 1:
-This document should explain the fields as listed on the VATSIM Flight Plan form using guidance located in the [[https://www.faa.gov/air_traffic/publications/atpubs/aim_html/appendix_4.html|FAA AIM]] and [[https://www.faa.gov/air_traffic/publications/atpubs/aip_html/appendix1.html|FAA AIP]]. The information derived has been significantly reduced for the purposes of the VA and therefore cannot be reliably used for real world use or flight planning.+This document should explain the fields as listed on the VATSIM Flight Plan form using guidance located in the [[https://www.faa.gov/air_traffic/publications/atpubs/aim_html/appendix_4.html|FAA AIM]],[[https://www.faa.gov/air_traffic/publications/atpubs/aip_html/appendix1.html|FAA AIP]],[[https://www.faa.gov/sites/faa.gov/files/FAA%20FPL%20Quick%20Reference%20Brochure%20%282022-09-15%29.pdf|FAA FPL Quick Reference Guide]], and [[https://www.faa.gov/sites/faa.gov/files/ERAS%20Flight%20Plan%20Interface%20Reference%20Guide%20%282022-10-01%29.pdf||FAA ERAM FPL Interface Guide]]. The information derived has been significantly reduced for the purposes of the VA and therefore cannot be reliably used for real world use or flight planning.
  
 ==== Callsign ==== ==== Callsign ====
Line 59: Line 59:
 | Z | Other equipment carried/other capabilities ((specify in Item 18 the other equipment carried or other capabilities, preceded by COM/, NAV/, and/or DAT, as appropriate)) | | Z | Other equipment carried/other capabilities ((specify in Item 18 the other equipment carried or other capabilities, preceded by COM/, NAV/, and/or DAT, as appropriate)) |
  
-The letter S may be used in lieu of VHF RTF, VOR, **AND** ILS (putting S is the same as putting LOV).+The letter S may be used in lieu of VHF RTF, VOR, **AND** ILS (putting S is the same as putting "LOV").
  
 ==== Transponder (ICAO 10b) ==== ==== Transponder (ICAO 10b) ====
Line 99: Line 99:
 List additional surveillance equipment or capabilities in Item 18 following the indicator SUR/. List additional surveillance equipment or capabilities in Item 18 following the indicator SUR/.
  
 +==== Departure ====
 +Enter the **FOUR** letter location identifier. The system //should// allow up to 11 characters, to allow for entry of fixes, intersection, fix/radial/distance, and lat/lon. If the system rejects the filing due to system limitations, enter ZZZZ and identify the departure airport in Item 18 (remarks) DEP/. A text description is permissible following DEP/.
 +
 +==== Departure Time ====
 +Indicate the expected dep. time using 4 digits in UTC/Zulu (HHMM).
 +
 +==== Altitude ====
 +Enter the initial requested cruise altitude, noting correct altitude for direction of flight rules.
 +
 +==== Airspeed ====
 +Enter the requested cruising TAS.
 +
 +==== Arrival ====
 +Enter the **FOUR** letter location identifier. See the notes under the "Departure" section; except the Item 18 field would be "DEST/" in lieu of "DEP/".
 +
 +==== Alternate ====
 +Enter the **FOUR** letter location identifier. If the airport does not have a 4 letter identifier, enter "ZZZZ" and note the airfield in Item 18 "ALTN/".
 +Alternate airports are not reported to ATC; this is an OPTIONAL part of the flight plan. While filing is not required, [[cocc:alternate_airports|rules for establishing alternate airports must be adhered to]].
 +
 +==== Enroute Time ====
 +Enter the total estimated elapsed time from departure to destination in HHMM format. This should not be BLOCK time; this should be AIR time.
 +.
 +==== Fuel Endurance ===
 +Enter the fuel endurance time in hours and minutes. This information is not transmitted to Air Traffic Control and is for SAR purposes.
 +
 +==== Route ====
 +File the route. Include SIDs and STARs. 
 +Hartlantair does not typically operate on "through" clearances, but... when filing a "through" clearance, indicate the delay after the location with an "oblique stroke" (/), followed by the letter D, the hour (HH), a plus symbol, and the minutes (MM) : /HH+MM
 +
 +Example: // EMI/D01+40 MAPEL V143 DELRO //
  
 ===== Item 18 / "Other" fields ===== ===== Item 18 / "Other" fields =====
 ==== PBN ==== ==== PBN ====
  
 +==== NAV ====
 +
 +==== DAT ====
 +
 +==== SUR ====
 +
 +==== DOF ====
 +FAA ATC systems will not accept flight plans more than 23 hours prior to their proposed departure time. FAA Flight Service and commercial flight planning services generally accept flight plans earlier and forward to ATC at an appropriate time, typically 2 to 4 hours before the flight. DOF is expressed in 6 digits: YYMMDD.
 +//DOF/171130//
 +
 +==== REG ====
 +The aircraft registration must be provided here if different from the Item 7 entry. The registration mark must not include any spaces or hyphens. Additionally, the actual aircraft registration must also be included if Item 7 would have contained a leading numeric and was modified to be prefixed with the appropriate alphabetic character for U.S. ATC acceptance.
 +
 +==== SEL ====
 +Flights with HF radio and Selective Calling capability should include their 4-letter SELCAL code. 
 +
 +//Shall is mandatory, Should is not//.
 +
 +==== CODE ====
 +There is no U.S. requirement to file the aircraft Mode S address (in hex, e.g. A519D9) in Item 18.
 +
 +==== RVR ====
 +RVR contains a 3-digit Runway Visual Range, expressed in meters. This is only included on the VATSIM page because of Eurocontrol shit - if you couldn't tell by the whole "meters" thing. Not forwarded to ATC.
 +
 +==== OPR ====
 +FAA has no requirements for inclusion of OPR/ in the flight plan. You are welcome to file OPR/HARTLANTAIR, though. Usually only required if not identifiable from the Aircraft ID.
 +
 +==== PER ====
 +Single Letter Aircraft Approach Category(( A grouping of aircraft based on a speed of 1.3 times the stall speed in the landing configuration at maximum gross landing weight. An aircraft must fit in only one category. If it is necessary to maneuver at speeds in excess of the upper limit of a speed range for a category, the minimums for the category for that speed must be used. For example, an aircraft which falls in Category A, but is circling to land at a speed in excess of 91 knots, must use the approach Category B minimums when circling to land.)) (Performance Category).
 +| Category | Approach Speed in knots |
 +| A | Less than 91|
 +|B | 91 to 120|
 +|C | 121 to 140 |
 +|D | 141 to 165 |
 +|E | 166 or greater |
 +
 +==== RALT ====
 +Enroute Alternate(s) - NOT REQUIRED for domestic US flights
 +
 +==== TALT ====
 +Take-off Alternate - NOT REQUIRED for domestic US flights
 +
 +==== ORGN ====
 +Flight Plan Origin - NOT REQUIRED for domestic US flights
 +
 +==== COM ====
 +Other communication capability
 +
 +==== EET ====
 +Estimated Elapsed Times in HHMM, with reference to FIR/ARTCC entry time. Maybe required? Not sure.
 +==== RMK ====
 +Enter that information that is pertinant to the flight... examples include:
 +NO SID
 +NO STAR
 +NO SID/STAR
 +DVRSN
 +CDR CAPABLE
 +
 +The inclusion of DVRSN indicates that the flight is requesting priority since it previously diverted.
 +
 +Additionally, according to the feds... Enter only those remarks pertinent to ATC or to the clarification of other flight plan information. Items of a personal nature are not accepted. Do not assume that remarks will be automatically transmitted to every controller. Specific ATC or en route requests should be made directly to the appropriate controller.
 +
 +Luckily, the AIM is not regulatory in nature :)