Airmen (Pilots, Mechanics, others) Forms. Airmen Certification; Flight Planning. Flight Plan; Pre-Flight Pilot Checklist and. The FAA will implement flight plan filing for civil aircraft using a format that aligns with The new format appears on FAA Form , FAA International Flight. Department of Defense flights who may continue to use the format prescribed in FAA Form , and sub part b, c, and d (below) do not.
|Published (Last):||19 December 2013|
|PDF File Size:||16.67 Mb|
|ePub File Size:||1.22 Mb|
|Price:||Free* [*Free Regsitration Required]|
Items 12 through 17 must be retained by the FSS or in the operational system and be available upon request. Part-time FSSs shall forward items 1 through fsa in accordance with para Transmit flight plans if necessary and flight plan amendments via interphone to the flight data position error referral position or departure sector when the aircraft’s proposed departure time is less than 15 minutes from transmittal time.
Transmit flight plans as follows:. When multiple two or more flight plans are received from the same aircraft, or for flight plans which propose alternating VFR and IFR, stopover, or terminal area delay, the station receiving the flight plans transmits separate flight plans to the appropriate ARTCCs for each IFR portion or segment.
Aerial refueling delays, or any other faaa route delays not covered in subparas a or b and not involving a change of altitude stratum, do not require separate messages. Delay information shall be filed within the route of flight. If a change of altitude stratum is indicated, transmit separate messages as in subparas a or b.
When a composite, stopover, or terminal area delay flight plan is revised: Before departure, transmit the information to the original addressees plus fqa new addressees. After departure, transmit the information to all new addresses who are affected by the change. When a flight is to depart after hours local time on the day following the filing of the flight plan, do not transmit the flight plan to the ARTCC until after hours local time.
For flights inbound to the conterminous U. Fza plan data messages must be addressed to the computer only.
Acknowledgements for all numbered messages will be received from the computer or the Flight Data position indicating receipt by the ARTCC, but not necessarily computer acceptance. Adhere to a fixed order of data. Do not exceed the stated maximum number of characters or elements allowed for each field in messages addressed to an ARTCC computer. Flight plans filed containing more than the stated character maximums should be sent using the ARTCC flight data address.
For manual entry into Service B, one space character must be entered at the end of each data field. The afa data field of a message need not be preceded by a space. The last data field of a message need not be followed by a space. Each field of data is composed of one or more elements. Discrete elements of information within a field are separated by delimiters, generally slashes fwa strokes or periods.
The prime consideration of these types of messages must be the readability of the transmitted data. Daa domestic flight data processing computers have the capability to return acknowledgments to the source and, depending on local adaption, return error messages and accept amendments. IFR flight plans specifying stopovers or 72331 area delays require separate messages be sent to the appropriate ARTCCs for each segment. Unless otherwise covered by a letter of agreement, treat flight plans proposing special use airspace delays in the same manner.
Separate messages are faz required for any other en route delays if a change of altitude stratum is proposed at the delay point. See subpara c14 h 1 [b] for delays not involving a change of altitude stratum. Some fields contain the necessary functions to operate the computer data terminal adapters and are designated by alpha characters. Do not separate these fields with spaces.
Start of Message Code Field A. Preamble 72233-1 Field B. Consists of originator, priority, and addressee s. Originator Line Field C.
Flight Plans: Don’t Leave Home Without One
Consists of a six-digit date-time group and the eight-character originator identifier. End of Line Function Field E. Same as subpara c1. Source Identification Field Nine or ten characters required followed by a space character in the following order: It is recommended that numbering systems be restarted with at the beginning of each day Z.
NOTE- There are no spaces between characters in subparas c5 aband c. Message Type Field The letters FP followed by a space character. Aircraft Identification Field Consists of two-to-seven alphanumeric characters followed by a space character.
The first character of the identification must be a letter. Aircraft Data Field Consists of two-to-nine characters followed by a space character.
Standard Briefing – FAA Form
Aircraft data within the field may vary from one-to-three elements consisting of: This element contains a maximum fza two characters followed by a slash.
This element is mandatory and contains two-to-four characters consisting of the authorized aircraft designator as contained in FAAO JO Enter military designators of aircraft, omitting prefixes and suffixes pertaining to aircraft mission or model. Consists of two-to-four characters followed by a space character. This field must indicate the filed true airspeed in knots or Mach number. Departure Point or Coordination Fix Field Consists of two-to-twelve characters followed by a space character.
This field contains the departure point or fix at which an aircraft will pick up IFR. It must be a fix, not an airway. For proposed departures, it must match the first element in the route of flight; and for IFR pickups, it must match either the first element in the route of flight or the third element if the.
Proposed Departure Time Field Consists of five or seven characters followed by a space character. Requested Altitude Field Consists of two-to-seven characters followed by a space character. Altitudes or flight levels, as 7323-1, must be expressed gaa hundreds of feet, but without leading zeros. The first occurrence of Field E must always follow Field 09 77233-1 the message. Any time a subsequent end of line becomes necessary, if used 723-31 Field 10, it must be preceded by the appropriate element separator not a space.
FAA Form 7233-1
If used within Field 11, Field E may be entered at any point within the remarks sequence. Route of Flight Field The route of flight consists of departure point 723-1 pickup point PUPthe route of flight, and normally a destination followed by a space character.
An element is separated from another element by a period character.
The foregoing does not apply if the first encountered fix happens to be the next filed junction point within the route. Double period insertions do not count against the element limitation. A fix must be filed in one of the following ways: Domestic, Canadian, and International identifiers of two-to-five alphanumeric characters. Consists of eight-to-eleven alphanumeric characters in the following sequence: Two-to-five characters identifying a navigational aid, three characters of azimuth expressed in degrees magnetic, and three characters of distance expressed in nautical miles from the navigational aid.
Zeros preceding a significant character must be entered before the azimuth and distance components as required to assure the transmission of three characters for each. Consists of nine-to-twelve characters entered as follows: If the optional letter is omitted, north is understood. If the optional letter is omitted, west is understood. A route must be filed in one of the following ways: The official airway designator must be filed.
Coded routes are a shorthand method of describing a route segment or segments which may have an altitude profile described, an adapted airspeed within the route, reentry or loop routes as an option, or a time delay at a fix within the route as an option. Some of the principal uses of coded routes are as follows: DP, if used, must be filed by the computer code designator as the second element of Field 10 and be followed by the transition or exit fix.
STAR, if used, must be filed by the computer code designator as the next to last element of Field 10 and immediately follow the entry or transition fix. Published radials for example, within a preferred route are considered airways. Do not file unpublished radials. The routes must be identified by an individual name.
NAR routes are numerically coded over existing airways and route systems from and to specific coastal fixes serving the North Atlantic.
A stereo route must specify a prestored stereo tag. An FP message may be entered with a stereo tag as the only Field 10 entry, which causes the Field 10 data stored for the stereo tag to be substituted for the stereo tag and processed as the filed Field Additionally, the filed departure point Field 06 must agree with the stored departure point. Must be appended to a fix.
The suffix is appended to the entry fix. Leading faaa are required, and the time en route is expressed in hours and minutes. If remarks Field 11 are present, a space is required after the last element of Field If remarks are not present, no space is required and Field F End of Message should be the next entry.