Section 2. Flight Plan Proposals

6-2-1. FLIGHT PLAN RECORDING

Record flight plans on FAA Form 7233-1, M1FC Domestic Flight Plan Mask, or in the OASIS Domestic Flight Plan dialog box. 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. Complete as follows:

NOTE-
OASIS. For detailed instructions on the Domestic Flight Plan dialog box, refer to the WINGS online help or the WINGS System Users Guide.

a. Item 1. Type of flight plan.

1. FAA Form 7233-1. Check the appropriate box.

2. M1FC- FR: field.

(a) V - civilian VFR flight plans including DVFR.

(b) MV - military VFR flight plans.

(c) PV - VFR flight plans departing from outside the facility's flight plan area.

(d) DV - Do not use. See para 6-6-3a.

(e) I - civil IFR flight plans or military IFR flight plans that do not require transmission of a flight notification message.

(f) MI - military IFR flight plans that require a flight notification message.

(g) PI - IFR flight plans departing from outside the facility's flight plan area that require a flight notification message.

NOTE-
1. M1FC. PI for transborder flights that require an ADCUS (Mexico) or CANPASS/GATE (Canada/US) flight notification message. PI messages are addressed to the departure tie-in station. They are in addition to the I message transmitted to the departure ARTCC. Remarks to be transmitted by the departure station as part of the flight notification message must be included in the PI message and preceded by a $ sign.

2. OASIS. IFR transborder flights that require an ADCUS (Mexico) flight notification message will be automatically addressed and transmitted to the departure ARTCC and the departure tie-in station if ADCUS is entered in remarks. To send an IFR Canadian flight plan departing from outside the facility's flight plan area that requires a flight notification message, enter the following in remarks: $CANPASS %ADCUS. OASIS uses the ADCUS to automatically address and transmit the flight plan to the departure tie-in station but the only remark transmitted is CANPASS. This is in addition to the message transmitted to the departure ARTCC.

(h) SC - Stereo flight plans for civil aircraft.

(i) SM - Stereo flight plans for military aircraft.

3. OASIS - Select type of flight plan from the Flight Rules (FR) drop down list:

(a) VFR - civilian VFR flight plans, including DVFR.

(b) IFR

(c) DVFR - Do not use. See para 6-6-3a.

(d) MIL VFR

(e) MIL IFR

(f) STEREO CVL

(g) STEREO MIL

(h) MIL IFR STOPOVER

(i) MIL VFR STOPOVER

(j) DVFR STOPOVER - Do not use.

b. Item 2. Aircraft Identification (M1FC- AI: field. OASIS - Aircraft ID text box). 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. 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

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

TBL 6-2-2
Canadian Military

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

NOTE-
OASIS. OASIS validates all aircraft types in accordance with FAAO JO 7340.2, Contractions. Nonstandard contractions will be rejected.

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-3.)

TBL 6-2-3
Suffix to Aircraft Type

Suffix to Aircraft Type (continued)

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-7 and TBL 2-3-7, Aircraft Equipment Suffix.

d. Item 4. True Airspeed (TAS Knots) (M1FC- TS: field. OASIS - Airspeed text box). 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.

1. M1FC- DD: field. 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.

NOTE-
Names may be used when there is no identifier available and they do not exceed 12 characters with no spaces. Unless a geographic point is converted to latitude/longitude or fix-radial-distance (FRD), the M1FC computer will not be able to provide weather/NOTAM information and the route override function must be used to transmit or modify the flight plan.

2. OASIS - Departure text box. Enter the departure point as follows: 2-5 alphanumeric character LOCID, 8-11 character fix-radial-distance or 9-12 character latitude/longitude.

f. Item 6. Departure Time.

1. M1FC- TM: field. Enter departure time in UTC. Prefix this time with a P in the TM: field for proposals or a D for departures. If the departure time is assumed, indicate this in the Remarks field.

2. OASIS - ETD text box. Enter the proposed or actual time of departure as follows: {(DD)HHMM : DD = 01-31, HH = 00-23, MM = 00-59}.

NOTE-
OASIS does not use prefixes (i.e., “P” or “D”) to determine a proposed or actual time of departure. This determination is made based on which button is used for filing.

g. Item 7. Cruising Altitude (M1FC- AE: field. OASIS - Enroute Altitude text box). 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 (M1FC- RT: field. OASIS - Route text box.). 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.

1. M1FC- AD: field. 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.

2. OASIS - Destination text box. Enter the destination airport or point over which the flight plan is to be cancelled as follows: 2-5 alphanumeric character LOCID, 8-11 character fix-radial-distance or 9-12 character latitude/longitude.

j. Item 10. Estimated Time Enroute (M1FC- TE: field. OASIS - Time Enroute text box). Enter in hours and minutes the total elapsed time between departure and destination; e.g., 0430 or 4+30. For IFR proposals, ETE must be in four-digit format; i.e., 0215.

NOTE-
OASIS facilities, enter the four digit enroute time in hours and minutes; hhmm: hh=00-99, mm=00-59.

k. Item 11. Remarks (M1FC- RM: field. OASIS - Remarks text box). 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 homebuilt aircraft (Veri-EZ, Long-EZ, Mustang, Delta Dart). For RM: field only - Use 1-80 characters beginning with *, #, $, or %. (See TBL 6-2-4.)

TBL 6-2-4

NOTE-
1. OASIS automatically inserts the appropriate symbol according to the flight plan type (i.e., $-VFR, * -IFR)

2. Civil aircraft with authorized company identification are required to file the full authorized radio call in remarks.

l. Item 12. Fuel on Board (M1FC- FB: field. OASIS - Fuel Capacity text box). Enter in hours and minutes; e.g., 0330 or 3+30.

NOTE-
OASIS facilities, enter the fuel capacity; hhmm: hh=00-99, mm=00-59.

m. Item 13. Alternate Airport/s.

1. (M1FC- AA: field). Enter the location identifier if specified by the pilot. For AA: field only. Use three-to-seven alphanumeric characters. For two alternate airports, enter identifiers consecutively; e.g., BJCFNL.

2. OASIS - Alternate Airport text box. Enter the location identifier of a single alternate airport in 3-4 alphanumeric characters. Additional alternate airports may be entered in the Remarks text box as nontransmitted information.

n. Item 14. Pilot's Name, Telephone Number, Aircraft's Home Base (M1FC- PD: field. OASIS - Pilot Data text box). 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 (M1FC- NB: field. OASIS - Number On Board text box). Self-explanatory.

p. Item 16. Color of Aircraft. (M1FC- CR: field. OASIS - Aircraft Color text box). Use authorized contractions when available. (See TBL 6-2-5.)

TBL 6-2-5
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. ENTRY OF MILITARY IFR MULTI-LEG 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-4. 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.