Section 2. Flight Plan Proposals

6-2-1. FLIGHT PLAN RECORDING

Record flight plans on FAA Form 7233-1, or electronic equivalent. Completion of all blocks or fields is not required in every case, and all items filed are not always transmitted. Use authorized abbreviations where possible. The instructions below are for completion of FAA Form 7233-1, Flight Plan. For electronic versions of flight plan forms, refer to that system's operating instructions.

NOTE-
Use FAA Form 7233-4, International Flight Plan, for international flights as well as flights in domestic U.S. airspace in which automatic assignment of RNAV routes is desired. See paragraph 6-2-3, Flight Plans with Area Navigation (RNAV) Routes in Domestic U.S. Airspace.

a. Item 1. Type of flight plan. Check the appropriate box.

b. Item 2. Aircraft Identification. Enter as follows, but do not exceed seven alphanumeric characters:

1. Civil Aircraft Including Air Carrier: Aircraft letter/digit registration including the letter T prefix for air taxi aircraft, the letter L for LIFEGUARD aircraft, or the three-letter aircraft company designator specified in FAAO JO 7340.2, Contractions followed by the trip or the flight number.

EXAMPLE-
N12345
TN5552Q
AAL192
LN751B

NOTE-
The letter L shall not be entered in Item 2 of the flight plan for air carrier or air taxi LIFEGUARD aircraft. Include the word LIFEGUARD in the remarks section of the flight plan.

2. U.S. Military Aircraft.

(a) Use the military abbreviation followed by the last five digits of the aircraft's number. For certain tactical mission aircraft, enter the assigned three-to-six letter code word followed by a one-to-four digit number. (See TBL 6-2-1)

TBL 6-2-1
Military

(b) Aircraft carrying the President, Vice President, and/or their family members will use the identifiers in the following tables. (See TBL 6-2-2 and TBL 6-2-3)

TBL 6-2-2
President and Family

TBL 6-2-3
Vice President and Family

3. Canadian Military Aircraft. The abbreviations shall be followed by a number group not to exceed four digits. (See TBL 6-2-4.)

TBL 6-2-4
Canadian Military

c. Item 3. Aircraft Type. Insert the name or abbreviation (two-to-four alphanumeric characters) of the manufacturer's or military designation. For amateur-built/experimental aircraft, use HXA, HXB, or HXC in accordance with the FAAO JO 7340.2, Contractions. Spell out aircraft type in Remarks.

1. Prefix to Aircraft Type (one-to-two alphanumeric characters). For IFR operations, if the aircraft's weight class is heavy, indicate this with the prefix “H”. If a formation flight is planned, enter the number and type of aircraft; e.g., 2H/B52.

2. Suffix to Aircraft Type (one alpha character). Indicate for IFR operations the aircraft's radar transponder, DME, or RNAV (includes LORAN) capability by adding the appropriate symbol preceded by a slant (/). (See TBL 6-2-5.)

TBL 6-2-5
Suffix to Aircraft Type

NOTE-
The /E and /F suffixes will only be used by aircraft operating to and from airports within the U.S., unless authorized by the controlling authority.

REFERENCE-
FAAO JO 7110.65, Para 2-3-8 and TBL 2-3-10, Aircraft Equipment Suffixes.

d. Item 4. True Airspeed (TAS Knots) Enter two-to- four digits for TAS in knots; M followed by three digits for Mach number; or SC for “speed classified.”

e. Item 5. Departure Point. Enter two-to-twelve alphanumeric and slant characters for name or identifier of the departure airport or point over which the flight plan is activated.

f. Item 6. Departure Time. Enter departure time in UTC.

g. Item 7. Cruising Altitude. Proposed altitude or flight level using two-to-seven characters; e.g., 80 or 080, OTP, OTP/125, VFR, ABV/060.

h. Item 8. Route of Flight. Enter identifiers for airways or jet routes to clearly indicate the proposed flight path. For direct flight, use names or identifiers of navigation aids, Navigation Reference System (NRS) waypoints, and geographical points or coordinates. If more than one airway or jet route is to be flown, clearly indicate the transition points.

NOTE-
1. On some direct flights beyond the departure center's airspace, it may be necessary to include a fix in the adjacent center's airspace or latitude/longitude coordinates, as appropriate, to facilitate computer acceptance. Local procedures should be applied to these special situations.

2. NRS waypoints consist of five alphanumeric characters, which include the ICAO Flight Information Region (FIR) identifier, followed by the letter corresponding to the FIR subset (ARTCC area for the contiguous U.S.), the latitude increment in single digit or group form, and the longitude increment.

EXAMPLE-
“KD34U”

i. Item 9. Destination. Enter two-to-twelve alphanumeric and/or slant characters for name or identifier of the destination airport or point over which the flight plan is to be cancelled.

j. Item 10. Estimated Time Enroute. Enter in hours and minutes the total elapsed time between departure and destination in four-digit format, i.e., 0215.

k. Item 11. Remarks. Information necessary for ATC or to assist search and rescue operations, plus any other data appropriate to the flight; e.g., the abbreviations FAA or DOT. Enter names of experimental or amateur-built aircraft (Veri-EZ, Long-EZ, Mustang, Delta Dart). For RM: field only - Use 1-80 characters beginning with *, #, $, or %. (See TBL 6-2-6.)

TBL 6-2-6
 

l. Item 12. Fuel on Board. Enter in hours and minutes in four-digit format; e.g., 0330.

m. Item 13. Alternate Airport/s. Enter the location identifier if specified by the pilot.

n. Item 14. Pilot's Name, Telephone Number, Aircraft's Home Base. Self-explanatory. For military pilots, obtain the name and telephone of BASOPS.

NOTE-
Pilot's name not required if BASOPS' name is provided.

o. Item 15. Number Aboard. Self-explanatory.

p. Item 16. Color of Aircraft. Use authorized contractions when available. (See TBL 6-2-7.)

TBL 6-2-7
Code and Color

NOTE-
1. For ICAO flight plans, see Appendix A.

2. Local procedures may be developed for use on the reverse side of FAA Form 7233-1.

6-2-2. OUTBOUNDS DEPARTING FROM OUTSIDE FLIGHT PLAN AREA

Accept flight plans regardless of departure point. Forward VFR flight plan proposals for aircraft proposing to depart from outside the facility's flight plan area to the tie-in FSS/AFSS for the departure point in the following format:

a. Type of Flight.

b. Aircraft Identification.

c. Aircraft Type.

d. Departure Point.

e. Destination.

f. Proposed Departure Time/ETE.

g. Remarks.

EXAMPLE-
AISR
FF KDAYYFYX
DTG KLOUYFYX
VFR N1234 BE9L DAY LOU P1330/0130

M1FC
FR:PV AI:N1234 AT:C150 TS:90 DD:DSM TM:P1800 AE:65 RT:DSM..OMA..LNK
AD:LNK TE:0300 RM:$FP KIKKYFYX
FB:0330 AA: PD:JOE PILOT
HB:DSM NB: CR:R/W TL:
OP:
CP:KFODYFYX
TA:2100

NOTE-
1. M1FC will autoaddress the CP field, automatically extract the required items from the flight plan mask and transmit a flight proposal to the departure tie-in AFSS/FSS.

M1FC will automatically fill in the originator of the flight plan in the RM field when the flight plan is transmitted.

2. For civil flight movement messages with remarks, precede the remarks with a dollar symbol ($).

3. OASIS will autoaddress the Closure Points field, automatically extract the required items from the flight plan, insert the originator of the flight plan into the Remarks field, and transmit a flight proposal to the departure tie-in AFSS/FSS at a time determined by the facility parameter.

6-2-3. FLIGHT PLANS WITH AREA NAVIGATION (RNAV) ROUTES IN DOMESTIC U.S. AIRSPACE

Use FAA Form 7233-4, International Flight Plan, for pilots filing flight plans in domestic U.S. airspace if automatic assignment of any of the following RNAV routes are desired: RNAV Standard Instrument Departure (SID); RNAV Standard Terminal Arrival Route (STAR); and/or RNAV Point-to-Point (PTP). For these flight plans, adhere to the following guidelines:

a. Item 10, Equipment. Enter “Z” in the equipment field in addition to other entries pertaining to radio communication, navigation and approach aids.

EXAMPLE-
SDGIWZ/S

b. Item 18, Other Information.

1. If the aircraft is RNAV 1 or RNAV 2 capable, enter “NAV/RNV” followed by the appropriate RNAV accuracy value:

(a) RNAV 1 SID, enter “D1”.

(b) RNAV 1 STAR, enter “A1”.

(c) En route RNAV, enter “E2”.
 

EXAMPLE-
NAV/RNVD1
NAV/RNVA1
NAV/RNVE2
NAV/RNVD1A1
NAV/RNVD1E2A1

NOTE-
The “D,” “E,” and “A” characters may appear in any order following “NAV/RNV.”

2. If the aircraft is RNAV PTP capable but not RNAV 1 and/or RNAV 2 capable, enter “RMK/PTP” and “NAV/RNVE99”.

EXAMPLE-
RMK/PTP NAV/RNVE99

NOTE-
Procedures contained in paragraph 6-2-3 do not apply to flights whose route remains entirely within Alaska domestic airspace.

6-2-4. ENTRY OF MILITARY IFR MULTILEG STOPOVER FLIGHT PLAN

a. Complete all FP fields down through time en route or remarks for the first leg. Use MI in the flight rules field. This will hold the flight plan on the proposed list for flight notification.

b. All subsequent legs shall be preceded by a slant and recorded in the route field after the first leg: DESTINATION, ETE, AIRSPEED, P-TIME, ALTI‐ TUDE, ROUTE, and remarks for each leg.

c. After all legs have been recorded properly, the FP should autoaddress the ARTCC of the first leg departure point in the OP: field and all destination BASOPS stations in the CP: field. GI will send the first leg to the appropriate ARTCC and place the flight plan on the proposed list.

EXAMPLE-
M1FC
FR:MI AI:BAT21 AT:F16/R TS:450 DD:DBQ TM:P1700 AE:280
RT:DBQ..TNU..OFF/FOE 0+15 450 P1800 270 OFF..FOE
AD:OFF TE:0030 RM:*REMARKS $VT012115
FB:0230 AA: PD:ON FILE BASOPS
HB:DBQ NB:1 CR:OD TL: OP:ZCG
CP:KOFFYXYX KFOEYXYX
TA:1730

d. To send the second leg of the flight plan to the appropriate ARTCC, the original flight plan needs to be altered.

1. Display the flight plan (FPC).

2. Change the MI to I. It is not necessary to hold this leg for flight notification.

3. Make the necessary changes to indicate the next leg of the flight plan.

EXAMPLE-
M1FC
FR:I AI:BAT21 AT:F16/R TS:450 DD:OFF TM:P1800 AE:270
RT:OFF..FOE
AD:FOE TE:0015 RM:*REMARKS
FB: AA: PD:ON FILE BASOPS
HB.DBQ NB:1 CR:OD TL: OP:ZCP
CP:
TA:1815

NOTE-
If there is an additional leg, it must be taken from the original flight plan.

e. After all legs have been sent to their appropriate ARTCC, construct a flight notification message.

1. Retrieve the original flight plan from the proposal list.

2. Edit each leg preceded by a slant to indicate the destination, ETE and pertinent remarks.

3. Delete all other information and restore to the proposal list (STPM) and await activation.

EXAMPLE-
M1FC
FR:MI AI:BAT21 AT:F16/R TS:450 DD:DBQ TM:P1700 AE:280
RT:DBQ..TNU..OFF/FOE 0+15
AD:OFF TE:0030 RM:*REMARKS $VTO12115
FB:0230 AA: PD:ON FILE BASOPS
HB:DBQ NB:1 CR:OD TL:
OP:ZCG
CP:KOFFYXYX KFOEYXYX
TA:

NOTE-
OASIS. Transmit only the applicable inbound and outbound flight notification information to intermediate tie-in facilities. Remarks common to all flight segments shall be entered in the Remarks text box for transmission. These remarks shall include: departure point, all stops and destination.

EXAMPLE-
DEPD TCM LNDG EDW DMA JAX ADW

NOTE-
OASIS. Detailed instructions for the processing of Military IFR Multi-Leg Stopover Flight Plans are contained in the WINGS online help and the WINGS System Users Guide.

6-2-5. ENTRY OF MILITARY VFR STOPOVER FLIGHT PLAN

a. File a military VFR stopover flight plan in the same format as a military IFR stopover.

b. After the flight plan is filed on the proposal list, display the flight plan (FP ACID). Use the CX keyword to cancel the flight plan. The complete flight plan is then on file for search and rescue.

EXAMPLE-
M1FC
FR:MV AI:G2034 AT:UH1/U TS:90 DD:FOD TM:P1800 AE:055
RT:FOD..DSM..OFF/MLC 3+10 90 P2100 045 OFF..MLC/SZL
2+10 90 P0100 055 MLC..SZL
AD:OFF TE:0200 RM:$VT010600
FB:0400 AA: PD:ON FILE BASOPS
HB:DBQ NB:1 CR:O/D TL:
OP:
CP:KOFFYXYX KMLCYFYX KSZLYXYX
TA:2000

c. After the flight plan is cancelled, use the FPC keyword to display the flight plan on the screen. Change the RT field to show only the destination, ETE, and any pertinent remarks for all remaining legs. File the revised version onto the proposal list to await activation.

EXAMPLE-
M1FC
FR:MV AI:G2034 AT:UH1/U TS:90 DD:FOD TM:P1800 AE:055
RT:FOD..DSM..OFF/MLC 3+10/SZL 2+10
AD:OFF TE:0200 RM:$VT010600
FB:0400 AA: PD:ON FILE BASOPS
HB:DBQ NB:1 CR:OD TL:
OP:
CP:KOFFYXYX KMLCYFYX KSZLYXYX
TA:2000

NOTE-
OASIS. Transmit only the applicable inbound and outbound flight notification information to intermediate tie-in facilities. Remarks common to all flight segments shall be entered in the Remarks text box for transmission. These remarks shall include: departure point, all stops and destination.

EXAMPLE-
DEPD TCM LNDG EDW DMA JAX ADW

NOTE-
OASIS. Detailed instructions for the processing of Military VFR Stopover Flight Plans are contained in the WINGS online help and the WINGS System Users Guide.