|
b. Latitude/longitude coordinates may be used to define waypoints and may be substituted for nonadapted NAVAIDs in space 25 of domestic en route flight progress strips provided it is necessary to accommodate a random RNAV or GNSS route request. c. Facility air traffic managers may authorize the optional use of spaces 13, 14, 14a, 22, 23, 24, and 28 for point out information, radar vector information, speed adjustment information, or transfer of control data. 2-3-3. OCEANIC DATA ENTRIES FIG 2-3-3
|
Block |
Information Recorded |
1. |
Mode 3/A beacon code, if applicable. |
2. |
Number of aircraft, if more than one, and type of aircraft. |
3. |
Aircraft identification. |
4. |
Reduced separation flags. |
5. |
Controlling sector number. |
6. |
Filed airspeed or assigned Mach number/True airspeed. |
7. |
Reported flight level. May contain an indicator for a flight that is climbing (↑) or descending (↓). Reports from Mode C, ADS or position reports are displayed in that order of preference. |
8. |
Cleared flight level. May contain an indicator for a future conditional altitude ( * ) that cannot be displayed. |
9. |
Requested flight level, if applicable. |
10. |
Previously reported position. |
11. |
Actual time over previously reported position. |
12. |
Last reported position. |
13. |
Actual time over last reported position. |
14. |
Next reporting position. |
15. |
In-conformance pilot's estimate or controller-accepted pilot's estimate for next reporting position. |
16. |
Future reporting position(s). |
17. |
System estimate for future reporting position(s). |
18. |
Departure airport or point of origin. |
19. |
Destination airport or filed point of flight termination. |
20. |
Indicators. Indicators and toggles for displaying or suppressing the display of the route of flight (F), second flight profile (2), radar contact (A), annotations (&), degraded Required Navigation Performance (RNP, indicator R) and clearance restrictions (X). |
21. |
Coordination indicator(s). |
22. |
Annotations. |
23. |
Clearance restrictions and conditions (may be multiple lines). |
24. |
Strip number and total number of strips (printed strips only). |
b. Standard annotations and abbreviations for Field 22 may be specified by facility directives.
2-3-4. TERMINAL DATA ENTRIES
a. Arrivals:
Information recorded on the flight progress strips (FAA Forms 7230-7.1, 7230-7.2, and 7230-8) shall be entered in the correspondingly numbered spaces. Facility managers can authorize omissions and/or optional use of spaces 2A, 8A, 8B, 9A, 9B, 9C, and 10-18, if no misunderstanding will result. These omissions and/or optional uses shall be specified in a facility directive.
TBL 2-3-3
Block |
Information Recorded |
1. |
Aircraft identification. |
2. |
Revision number (FDIO locations only). |
2A. |
Strip request originator. (At FDIO locations this indicates the sector or position that requested a strip be printed.) |
3. |
Number of aircraft if more than one, heavy aircraft indicator "H/" if appropriate, type of aircraft, and aircraft equipment suffix. |
4. |
Computer identification number if required. |
5. |
Secondary radar (beacon) code assigned. |
6. |
(FDIO Locations.) The previous fix will be
printed. |
7. |
Coordination fix. |
8. |
Estimated time of arrival at the coordination fix or destination airport. |
8A. |
OPTIONAL USE. |
8B. |
OPTIONAL USE, when voice recorders are
operational; |
9. |
Altitude (in hundreds of feet) and remarks. |
NOTE- |
Altitude information may be written in thousands of feet provided the procedure is authorized by the facility manager, and is defined in a facility directive, i. e., FL 230 as 23, 5,000 feet as 5, and 2,800 as 2.8. |
9A. |
Minimum fuel, destination airport/point out/radar vector/speed adjustment information. Air traffic managers may authorize in a facility directive the omission of any of these items, except minimum fuel, if no misunderstanding will result. |
NOTE- |
Authorized omissions and optional use of spaces shall be specified in the facility directive concerning strip marking procedures. |
9B. |
OPTIONAL USE. |
9C. |
OPTIONAL USE. |
10-18. |
Enter data as specified by a facility directive. Radar facility personnel need not enter data in these spaces except when nonradar procedures are used or when radio recording equipment is inoperative. |
b. Departures:
Information recorded on the flight progress strips (FAA Forms 7230-7.1, 7230-7.2, and 7230-8) shall be entered in the correspondingly numbered spaces. Facility managers can authorize omissions and/or optional use of spaces 2A, 8A, 8B, 9A, 9B, 9C, and 10-18, if no misunderstanding will result. These omissions and/or optional uses shall be specified in a facility directive.
TBL 2-3-4
Block |
Information Recorded |
1. |
Aircraft identification. |
2. |
Revision number (FDIO locations only). |
2A. |
Strip request originator. (At FDIO locations this indicates the sector or position that requested a strip be printed.) |
3. |
Number of aircraft if more than one, heavy aircraft indicator "H/" if appropriate, type of aircraft, and aircraft equipment suffix. |
4. |
Computer identification number if required. |
5. |
Secondary radar (beacon) code assigned. |
6. |
Proposed departure time. |
7. |
Requested altitude. |
NOTE- |
Altitude information may be written in thousands of feet provided the procedure is authorized by the facility manager, and is defined in a facility directive, i. e., FL 230 as 23, 5,000 feet as 5, and 2,800 as 2.8. |
8. |
Departure airport. |
8A. |
OPTIONAL USE. |
8B. |
OPTIONAL USE, when voice recorders are
operational; |
9. |
Computer-generated: Route, destination, and remarks. Manually enter altitude/altitude restrictions in the order flown, if appropriate, and remarks. |
9. |
Hand-prepared: Clearance limit, route, altitude/altitude restrictions in the order flown, if appropriate, and remarks. |
NOTE- |
Altitude information may be written in thousands of feet provided the procedure is authorized by the facility manager, and is defined in a facility directive, i.e., FL 230 as 23, 5,000 feet as 5, and 2,800 as 2.8. |
9A. |
OPTIONAL USE. |
9B. |
OPTIONAL USE. |
9C. |
OPTIONAL USE. |
10-18. |
Enter data as specified by a facility directive. Items, such as departure time, runway used for takeoff, check marks to indicate information forwarded or relayed, may be entered in these spaces. |
c. Overflights:
Information recorded on the flight progress strips (FAA Forms 7230-7.1, 7230-7.2, and 7230-8) shall be entered in the correspondingly numbered spaces. Facility managers can authorize omissions and/or optional use of spaces 2A, 8A, 8B, 9A, 9B, 9C, and 10-18, if no misunderstanding will result. These omissions and/or optional uses shall be specified in a facility directive.
TBL 2-3-5
Block |
Information Recorded |
1. |
Aircraft identification. |
2. |
Revision number (FDIO locations only). |
2A. |
Strip request originator. (At FDIO locations this indicates the sector or position that requested a strip be printed.) |
3. |
Number of aircraft if more than one, heavy aircraft indicator "H/" if appropriate, type of aircraft, and aircraft equipment suffix. |
4. |
Computer identification number if required. |
5. |
Secondary radar (beacon) code assigned. |
6. |
Coordination fix. |
7. |
Overflight coordination indicator (FDIO locations only). |
NOTE- |
The overflight coordination indicator identifies the facility to which flight data has been forwarded. |
8. |
Estimated time of arrival at the coordination fix. |
8A. |
OPTIONAL USE. |
8B. |
OPTIONAL USE, when voice recorders are
operational; |
9. |
Altitude and route of flight through the terminal area. |
NOTE- |
Altitude information may be written in thousands of feet provided the procedure is authorized by the facility manager, and is defined in a facility directive, i.e., FL 230 as 23, 5,000 feet as 5, and 2,800 as 2.8. |
9A. |
OPTIONAL USE. |
9B. |
OPTIONAL USE. |
9C. |
OPTIONAL USE. |
10-18. |
Enter data as specified by a facility directive. |
NOTE-
National standardization of items (10 through 18) is not
practical because of regional and local variations in
operating methods; e.g., single fix, multiple fix, radar,
tower en route control, etc.
d. Air traffic managers at automated terminal radar facilities may waive the requirement to use flight progress strips provided:
1. Backup systems such as multiple radar sites/systems or single site radars with CENRAP are utilized.
2. Local procedures are documented in a facility directive. These procedures should include but not be limited to:
(a) Departure areas and/or procedures.
(b) Arrival procedures.
(c) Overflight handling procedures.
(d) Transition from radar to nonradar.
(e) Transition from ARTS to non-ARTS.
(f) Transition from ASR to CENRAP.
(g) Transition to or from ESL.
3. No misunderstanding will occur as a result of no strip usage.
4. Unused flight progress strips, facility developed forms and/or blank notepads shall be provided for controller use.
5. Facilities shall revert to flight progress strip usage if backup systems referred to in subpara d1 are not available.
e. Air traffic managers at FDIO locations may authorize reduced lateral spacing between fields so as to print all FDIO data to the left of the strip perforation. When using FAA Form 7230-7.2, all items will retain the same relationship to each other as they do when the full length strip (FAA Form 7230-7.1) is used.
2-3-5. AIRCRAFT IDENTITY
Indicate aircraft identity by one of the following using combinations not to exceed seven alphanumeric characters:
a. Civil aircraft, including air-carrier aircraft letter-digit registration number including the letter "T" prefix for air taxi aircraft, the letter "L" for lifeguard aircraft, 3-letter aircraft company designator specified in FAAO JO 7340.2, Contractions, followed by the trip or flight number. Use the operating air carrier's company name in identifying equipment interchange flights.
EXAMPLE-
"N12345."
"TN5552Q."
"AAl192."
"LN751B."
NOTE-
The letter "L" is not to be used for air carrier/air taxi
lifeguard aircraft.
b. Military Aircraft.
1. Prefixes indicating branch of service and/or type of mission followed by the last 5 digits of the serial number (the last 4 digits for CFC and CTG). (See TBL 2-3-6 and TBL 2-3-7.)
2. Pronounceable words of 3, 4, 5, and 6 letters followed by a 4-, 3-, 2-, or 1-digit number.
EXAMPLE-
"SAMP Three One Six."
3. Assigned double-letter 2-digit flight number.
4. Navy or Marine fleet and training command aircraft, one of the following:
(a) The service prefix and 2 letters (use
phonetic alphabet equivalent) followed by 2 or
3 digits.
TBL 2-3-6
Branch of Service Prefix
Prefix |
Branch |
A |
U.S. Air Force |
C |
U.S. Coast Guard |
G |
Air or Army National Guard |
R |
U.S. Army |
VM |
U.S. Marine Corps |
VV |
U.S. Navy |
CFC |
Canadian Forces |
CTG |
Canadian Coast Guard |
TBL 2-3-7
Military Mission Prefix
Prefix |
Mission |
E |
Medical Air Evacuation |
F |
Flight Check |
L |
LOGAIR (USAF Contract) |
RCH |
AMC (Air Mobility Command) |
S |
Special Air Mission |
(b) The service prefix and a digit and a letter (use phonetic alphabet equivalent) followed by 2 or 3 digits.
5. Aircraft carrying the President, Vice President, and/or their family members will use the identifiers in the following tables. See TBL 2-3-8 and TBL 2-3-9.
TBL 2-3-8
President and Family
Service |
President |
Family |
Air Force |
AF1 |
AF1F |
Marine |
VM1 |
VM1F |
Navy |
VV1 |
VV1F |
Army |
RR1 |
R1F |
Coast Guard |
C1 |
C1F |
Guard |
G1 |
G1F |
Commercial |
EXEC1 |
EXEC1F |
TBL 2-3-9
Vice President and Family
Service |
Vice President |
Family |
Air Force |
AF2 |
AF2F |
Marine |
VM2 |
VM2F |
Navy |
VV2 |
VV2F |
Army |
RR2 |
R2F |
Coast Guard |
C2 |
C2F |
Guard |
G2 |
G2F |
Commercial |
EXEC2 |
EXEC2F |
c. Special-use. Approved special-use identifiers.
2-3-6. AIRCRAFT TYPE
Use the approved codes listed in Appendix A through Appendix C to indicate aircraft type.
2-3-7. USAF/USN UNDERGRADUATE PILOTS
To identify aircraft piloted by solo USAF/USN undergraduate student pilots (who may occasionally request revised clearances because they normally are restricted to flight in VFR conditions), the aircraft identification in the flight plan shall include the letter “Z” as a suffix. Do not use this suffix, however, in ground‐to‐air communication.
NOTE-
USAF solo students who have passed an instrument
certification check may penetrate cloud layers in climb or
descent only. Requests for revised clearances to avoid
clouds in level flight can still be expected. This does not
change the requirement to use the letter “Z” as a suffix to
the aircraft identification.
REFERENCE-
FAAO JO 7110.65, Para
2-4-20, Aircraft Identification.
FAAO JO 7610.4, Chapter 12, Section 10, USAF Undergraduate
Flying Training (UFT)/Pilot Instructor Training (PIT)/Introduction To
Fighter Fundamentals.
2-3-8. AIRCRAFT EQUIPMENT SUFFIX
a. Indicate, for both VFR and IFR operations, the aircraft's radar transponder, DME, or navigation capability by adding the appropriate symbol, preceded by a slant. (See TBL 2-3-10.)
b. When forwarding this information, state the aircraft type followed by the word “slant” and the appropriate phonetic letter equivalent of the suffix.
EXAMPLE-
“Cessna Three-ten slant Tango.”
“A-Ten slant November.”
“F-Sixteen slant Papa.”
“Seven-sixty-seven slant Golf.”
c. Utilize aircraft equipment suffix /H to indicate “RVSM-capable, no transponder.”
NOTE-
/H is for ATC use only. Users are not authorized to file this
suffix.
2-3-9. CLEARANCE STATUS
Use an appropriate clearance symbol followed by a dash (-) and other pertinent information to clearly show the clearance status of an aircraft. To indicate delay status use:
a. The symbol “H” at the clearance limit when holding instructions have been included in the aircraft's original clearance. Show detailed holding information following the dash when holding differs from the established pattern for the fix; i.e., turns, leg lengths, etc.
b. The symbols “F” or “O” to indicate the clearance limit when a delay is not anticipated.
TBL 2-3-10
Aircraft Equipment Suffixes
Suffix |
Aircraft Equipment Suffixes |
|
NO DME |
/X |
No transponder |
/T |
Transponder with no Mode C |
/U |
Transponder with Mode C |
|
DME |
/D |
No transponder |
/B |
Transponder with no Mode C |
/A |
Transponder with Mode C |
|
TACAN ONLY |
/M |
No transponder |
/N |
Transponder with no Mode C |
/P |
Transponder with Mode C |
|
AREA NAVIGATION (RNAV) |
/Y |
LORAN, VOR/DME, or INS with no transponder |
/C |
LORAN, VOR/DME, or INS, transponder with no Mode C |
/I |
LORAN, VOR/DME, or INS, transponder with Mode C |
|
ADVANCED RNAV WITH TRANSPONDER AND MODE C (If an aircraft is unable to operate with a transponder and/or Mode C, it will revert to the appropriate code listed above under Area Navigation.) |
/E |
Flight Management System (FMS) with DME/DME and IRU position updating |
/F |
Flight Management System (FMS) with DME/DME position updating |
/G |
Global Navigation Satellite System (GNSS), including GPS or WAAS, with en route and terminal capability |
/R |
Required Navigational Performance. The aircraft meets the RNP type prescribed for the route segment(s), route(s) and/or area concerned. |
|
REDUCED VERTICAL SEPARATION MINIMUM (RVSM). Prior to conducting RVSM operations within the U.S., the operator must obtain authorization from the FAA or from the responsible authority, as appropriate. |
/J |
/E with RVSM |
/K |
/F with RVSM |
/L |
/G with RVSM |
/Q |
/R with RVSM |
/W |
RVSM |
2-3-10. CONTROL SYMBOLOGY
Use authorized control and clearance symbols or abbreviations for recording clearances, reports, and instructions. Control status of aircraft must always be current. You may use:
a. Plain language markings when it will aid in understanding information.
b. Locally approved identifiers. Use these only within your facility and not on teletypewriter or interphone circuits.
c. Plain sheets of paper or locally prepared forms to record information when flight progress strips are not used. (See TBL 2-3-11 and TBL 2-3-12.)
d. Control Information Symbols.
(See FIG 2-3-7 and FIG 2-3-8.)
REFERENCE-
FAAO JO 7110.65, Para
4-5-3, Exceptions.
TBL 2-3-11
Clearance Abbreviations
Abbreviation |
Meaning |
A |
Cleared to airport (point of intended landing) |
B |
Center clearance delivered |
C |
ATC clears (when clearance relayed through non-ATC facility) |
CAF |
Cleared as filed |
D |
Cleared to depart from the fix |
F |
Cleared to the fix |
H |
Cleared to hold and instructions issued |
L |
Cleared to land |
N |
Clearance not delivered |
O |
Cleared to the outer marker |
PD |
Cleared to climb/descend at pilot's discretion |
Q |
Cleared to fly specified sectors of a NAVAID defined in terms of courses, bearings, radials or quadrants within a designated radius. |
T |
Cleared through (for landing and takeoff through intermediate point) |
V |
Cleared over the fix |
X |
Cleared to cross (airway, route, radial) at (point) |
Z |
Tower jurisdiction |
TBL 2-3-12
Miscellaneous Abbreviations
Abbreviation |
Meaning |
BC |
Back course approach |
CT |
Contact approach |
FA |
Final approach |
FMS |
Flight management system approach |
GPS |
GPS approach |
I |
Initial approach |
ILS |
ILS approach |
MA |
Missed approach |
MLS |
MLS approach |
NDB |
Nondirectional radio beacon approach |
OTP |
VFR conditions-on-top |
PA |
Precision approach |
PT |
Procedure turn |
RA |
Resolution advisory (Pilot reported TCAS event) |
RH |
Runway heading |
RNAV |
Area navigation approach |
RP |
Report immediately upon passing (fix/altitude) |
RX |
Report crossing |
SA |
Surveillance approach |
SI |
Straight-in approach |
TA |
TACAN approach |
TL |
Turn left |
TR |
Turn right |
VA |
Visual approach |
VR |
VOR approach |
FIG 2-3-7
Control Information Symbols [Part 1]
FIG 2-3-8
Control Information Symbols [Part 2]