Skip to Main Content
FlightPushFLIGHTPUSH
Chapter 4

Learn

Dashboard My Courses Mastery Map Practice Flight Bag

Resources

CFR & AIM FAA Orders Handbooks & Guides Certification Standards Pilot/Controller Glossary Advisory Circulars Legal Interpretations
Safety Center
Articles Trust Center
Help Center FAQ Status
  1. Reference Library
  2. FAA Orders
  3. JO 7110.10
  4. Chapter 4
  5. Section 1
Loading
flightpush.co home
JO 7110.10 Flight Services
  1. Chapter 1. General

    Section 1. Introduction
  2. Section 2. Terms of Reference
  3. Chapter 2. General Control

    Section 1. General
  4. Section 2. Interphone Communications
  5. Section 3. General Phraseology
  6. Section 4. Weather Phraseology
  7. Section 5. Aviation Phraseology
  8. Chapter 3. Emergency Services

    Section 1. General
  9. Section 2. Emergency Assistance
  10. Section 3. Aircraft Orientation
  11. Section 4. Overdue Aircraft
  12. Section 5. International SAR
  13. Chapter 4. In‐Flight Services

    Section 1. General
    1. 4-1-1 DESCRIPTION
    2. 4-1-2 PRE‐DUTY REQUIREMENTS
    3. 4-1-3 OPERATIONAL PRIORITY
    4. 4-1-4 IN‐FLIGHT WEATHER BRIEFINGS
    5. 4-1-5 AIRCRAFT‐REPORTED NAVIGATIONAL EQUIPMENT MALFUNCTIONS
    6. 4-1-6 RECORDING IN‐FLIGHT INFORMATION
    7. 4-1-7 FLIGHT PROGRESS STRIPS AND ENTRY DATA
  14. Section 2. Radio Communications
  15. Section 3. Advisory Services
  16. Section 4. Automatic Flight Information Service (AFIS)
  17. Section 5. Airport Lighting and Visibility Aids
  18. Section 6. Special VFR Operations
  19. Chapter 5. Pre‐Flight Services

    Section 1. General
  20. Section 2. Pilot Briefing
  21. Section 3. Briefing Display
  22. Chapter 6. Flight Data Services

    Section 1. General
  23. Section 2. Flight Plan Handling
  24. Section 3. Military Operations
  25. Section 4. International Operations and Messages
  26. Section 5. Customs Notifications and ADIZ Requirements
  27. Section 6. Canadian Movement and Control Messages (Transborder Flights Only)
  28. Section 7. Mexican Movement and Control Messages (Transborder Flights Only)
  29. Chapter 7. NOTAM Services

    Section 1. General
  30. Section 2. NOTAM Handling
  31. Chapter 8. FAA Weather Services

    Section 1. Pilot Weather Reports
  32. Section 2. Surface Weather Observations
  33. Section 3. Aviation Weather Cameras
  34. Section 4. Future FAA Weather Services
  35. Appendices

    Appendix A. FAA Form 7233-4, International Flight Plan
  36. Appendix B. FAA Form 7233-1, Flight Plan
  37. Appendix C. Other FAA Forms
  38. Appendix D. Service B Message Formats

JO 7110.10 Flight Services|JO 7110.10EE · Change 3 · Effective 7/9/2026

Chapter 4 · Section 1

General

7 Paragraphs|4-1-1–4-1-7

Read Citation (on FlightPush)

4-1-1 DESCRIPTION

In-flight services are those provided to or affecting aircraft in-flight or otherwise operating on the airport surface. This includes services to airborne aircraft, such as:

a.

ATC clearance relay.

b.

Voice communications for designated portions of ARTCC airspace.

c.

Flight progress reports.

d.

Advisories or requests.

e.

Issuance of military flight advisory messages.

f.

NOTAM delivery.

g.

SAR communications searches.

h.

Flight plan handling.

i.

Transcribed or live broadcasts.

j.

Weather observations.

k.

PIREP solicitation and dissemination.

l.

Pilot briefings.

4-1-2 PRE‐DUTY REQUIREMENTS

a.

Familiarization. Prior to assuming in-flight duties, specialists must familiarize themselves with meteorological and aeronautical conditions in accordance with appropriate facility directives. After assuming duties, specialists must continue to review data during the watch to maintain comprehensive knowledge of conditions affecting operations. This includes:

1.

General locations of weather-causing systems and general weather conditions.

2.

Detailed information of current and forecast weather conditions for the assigned FPA or AOR.

3.

Aeronautical information; particularly, NOTAMs, SUAs, TFRs, and air traffic delays.

b.

Transfer of position responsibility. Specialists must accomplish the transfer of position responsibility in accordance with paragraph 2-1-3, Transfer of Position Responsibility, of this order.

4-1-3 OPERATIONAL PRIORITY

Provide in‐flight services in accordance with the procedures in this chapter to aircraft on a “first come, first served” basis, as circumstances permit.

a.

Aircraft in distress have priority over all other aircraft.

NOTE

Refer to paragraph 3-1-3 for information on providing assistance for emergency services.

b.

Treat air ambulance flights as follows:

1.

Provide priority handling to civilian air ambulance flights when the pilot, in radio transmissions, verbally identifies the flight by stating “MEDEVAC” followed by the FAA authorized call sign or the full civilian registration letters/numbers. Specialists must use good judgment in each situation to facilitate the most expeditious movement of a MEDEVAC aircraft.

NOTE

If a flight plan includes the letter “L” for “MEDEVAC” and/or includes “MEDEVAC” in Item 11 (Remarks) of the flight plan or Item 18 (Other Information) of an international flight plan, the entries are considered informational in nature only and not an identification for operational priority.

REFERENCE

FAA Order JO 7110.10, Para 2-5-3, Aircraft Identification.

2.

Provide priority handling to AIR EVAC and HOSP flights when verbally requested by the pilot.

NOTE

If a flight plan includes “HOSP” or “AIR EVAC” in either Item 11 (Remarks) of the flight plan or Item 18 (Other Information) of an international flight plan, the entries are considered informational in nature only and not an identification for operational priority.

3.

Assist the pilots of MEDEVAC, AIR EVAC, and HOSP aircraft to avoid areas of significant weather and adverse conditions.

4.

If requested by a MEDEVAC, AIR EVAC, or HOSP pilot, provide additional assistance (for example, landline notifications) to expedite ground handling of patients, vital organs, or urgently needed medical materials.

c.

Provide maximum assistance to aircraft performing a SAR mission.

d.

Provide special handling to expedite, as required, to aircraft engaged in flight inspections, also known as Flight Check. Unless otherwise agreed to, maintain direct contact with the pilot and provide information regarding known traffic in the area and request the pilot's intentions.

NOTE

1. Many flight inspections are accomplished using automatic recording equipment. An uninterrupted flight is necessary for successful completion of the mission. The workload for the limited number of aircraft engaged in these activities requires strict adherence to a schedule. 2. Flight inspection operations that require special participation of ground personnel, specific communications, or radar operation capabilities are considered to require special handling. These flights are coordinated with appropriate facilities before departure.

4-1-4 IN‐FLIGHT WEATHER BRIEFINGS

a.

Upon request, provide en route aircraft with pertinent weather information applicable to the phase of flight, altitude, and/or route.

b.

Provide in‐flight weather briefings in accordance with the procedures outlined in Chapter 5, Pre‐Flight Services.

c.

When conditions dictate, provide information for alternate routes and/or altitudes to assist the pilot in the avoidance of hazardous flight conditions.

4-1-5 AIRCRAFT‐REPORTED NAVIGATIONAL EQUIPMENT MALFUNCTIONS

a.

Aircraft-reported NAVAID malfunctions are subject to varying circumstances. When an aircraft reports a ground‐based NAVAID malfunction, take the following action:

1.

Request a report from a second aircraft.

2.

If the second aircraft reports normal operations, if able, inform the first aircraft. Record the incident on FAA Form 7230-4, Daily Record of Facility Operation.

3.

If the second aircraft confirms the malfunction:

(a)

Notify the appropriate IFR control facility or sector.

(b)

Notify Tech Ops personnel.

(c)

Take NOTAM action when requested by Tech Ops personnel.

(d)

Record the incident on FAA Form 7230-4.

4.

In the absence of a second aircraft report:

(a)

Notify Tech Ops and advise what time the initial aircraft reported the failure and when a second aircraft report might be obtained.

(b)

Record the incident on FAA Form 7230-4.

b.

When an aircraft reports GPS/GNSS anomaly:

1.

Request the following information:

(a)

Aircraft call sign and type of aircraft.

(b)

Date and time of the occurrence.

(c)

Location of anomaly.

(d)

Altitude.

2.

Record the incident on FAA Form 7230-4.

3.

Forward this information to the traffic management unit and Tech Ops personnel.

c.

When an aircraft reports a WAAS anomaly, request the following information and/or take the following actions:

1.

Determine if the pilot has lost all WAAS service.

EXAMPLE

“Are you receiving any WAAS service?”

2.

If the pilot reports receipt of any WAAS service, acknowledge the report, and continue normal operations.

3.

If the pilot reports loss of all WAAS service, report as a GPS anomaly using procedures in subparagraph 4-1-5b.

d.

When an aircraft reports an ADS-B services malfunction (for example, ADS-B, TIS-B, FIS-B, or ADS-R):

1.

Request the following information:

(a)

Aircraft call sign and type of aircraft.

(b)

Date and time of observation.

(c)

Location and altitude of anomaly.

(d)

Condition observed (or anomaly).

(e)

Type and software version of avionics system.

2.

Forward this information to an OCC or SOC as appropriate.

3.

Record the incident on FAA Form 7230-4.

4-1-6 RECORDING IN‐FLIGHT INFORMATION

a.

Record all actions taken in the provision of in-flight services.

1.

Aircraft contacts.

(a)

When using flight progress strips, if the station has the aircraft's flight plan, enter “FP” in item 14 on the strip to show the flight plan is on file at the facility.

(b)

If there is no flight plan on file for the aircraft, specialists must obtain the following from the aircraft:

(1)

Aircraft identification.

(2)

Type of flight.

(3)

Time of contact.

(4)

Other operationally significantitems.

(c)

If the in-flight position is recorded, you may limit entries in the aircraft contact portion of the strip to those necessary for your use.

(d)

The following should be logged using the symbols in TBL 4-1-1 and TBL 4-1-2:

(1)

Type of briefing – standard, abbreviated, or outlook.

(2)

Type of flight – IFR, VFR, or DVFR.

(3)

Category of flight – air carrier, air taxi, military, or general aviation.

(4)

Aircraft identification.

(5)

Type of service – airport advisory, clearance request.

(6)

Remarks. Operating position if not automatically logged by the operational system.

TBL 4-1-1 Clearance Abbreviations

AbbreviationMeaning
ACleared to airport (point of intended landing)
BARTCC clearance delivered
CATC clears (when clearance relayed through non-ATC facility)
CAFCleared as filed
DCleared to depart from the fix
FCleared to the fix
HCleared to hold and instructions issued
LCleared to land
NClearance not delivered
OCleared to the outer marker
PDCleared to climb/descend at pilot's discretion
QCleared to fly specified sectors of a NAVAID defined in terms of courses, bearings, radials, or quadrants within a designated radius
TCleared through (for landing and takeoff through intermediate point)
VCleared over the fix
XCleared to cross (airway, route, radial) at (point)
ZTower jurisdiction

TBL 4-1-2 Miscellaneous Abbreviation

AbbreviationMeaning
BCBack course approach
CTContact approach
FAFinal approach
GPSGPS approach
IInitial approach
ILSILS approach
MAMissed approach
NDBNon-directional radio beacon approach
OTPVFR conditions-on-top
PAPrecision approach
PTProcedure turn
RHRunway heading
RPReport immediately upon passing (fix/altitude)
RXReport crossing
SASurveillance approach
SIStraight‐in approach
TATACAN approach
TLTurn left
TRTurn right
VAVisual approach
VRVOR approach
2.

Flight plans and related messages (for example, modifications, cancellations, activations, and closures). When closing an active VFR flight plan, obtain departure point and destination, if not already known.

NOTE

1. A closed VFR flight plan is one that has been activated and is then removed from an inbound list. 2. A canceled VFR flight plan is one that is removed from a proposed list and has not been activated. 3. FSS operational systems contain an electronic equivalent of authorized FAA flight plan forms.

3.

ATC clearances.

4.

Pilot briefings.

5.

Weather and flight data messages.

6.

Other operationally significant actions.

b.

In‐flight contacts may be logged in the operational system, the multi‐touch electronic flight strip (EFS) system, or other facility approved alternate forms.

c.

Locally approved procedures may be used to manually record data during heavy traffic periods or system outages and should be logged in the operational system as soon as practicable.

d.

Use control/clearance symbols, abbreviations, location identifiers, and contractions for recording position reports, traffic clearances, and other data.

e.

When recording data, you may use:

1.

Plain language to supplement data when it will aid in understanding the recorded information.

2.

Locally approved contractions and identifiers for frequently used terms and local fixes not listed in FAA Order JO 7340.2, Contractions, or accessible through FAA Order JO 7350.9, Location Identifiers. Use only within your facility, not on data or interphone circuits. All locally approved contractions and identifiers must be available in facility files for record and reference purposes.

f.

When recording data manually, use the standard hand-printed characters shown in TBL 4-1-3 to prevent misinterpretation.

1.

To correct or update data, draw a horizontal line through it and write the correct information adjacent to it.

2.

Do not erase any item.

TBL 4-1-3 Hand Printed Character Chart

TypedHand‐PrintedTypedHand‐Printed
AASS
BBTT
CCUU
DDVV
EEWW
FFXX
GGYY
HHZƵ
II1l
JJ22
KK33
LL44
MM55
NN66
OO77
PP88
QQ99
RR0Ø

NOTE

A slant line crossing through the numeral zero and an underline of the letter “S” on handwritten portions of flight progress strips are required only when there is reason to believe the lack of these markings could lead to a misunderstanding. A slant line through the numeral zero is required on all weather data.

4-1-7 FLIGHT PROGRESS STRIPS AND ENTRY DATA

a.

When officially used to record in-flight data, use the multi‐touch EFS to record:

1.

Aircraft contacts.

2.

ATC clearances.

3.

Pilot briefings on airborne aircraft.

4.

Other operationally significant items.

b.

Locally approved procedures may be used to manually record flight progress during heavy traffic periods or system outages and should be logged in the multi-touch EFS as soon as practicable.

c.

Use a flight progress strip for each aircraft and record all contacts with that aircraft on the same strip. If supplemental strips are needed for additional writing space, keep the original and supplemental strips together.

NOTE

Multiple flights by the same aircraft may be recorded on a single strip when situational awareness and strip bay efficiency are improved.

d.

Flight progress strip (see FIG 4-1-1).

FIG 4-1-1 Flight Progress Strip

e.

Flight progress strip entry examples (see FIG 4-1-2 and FIG 4-1-3).

FIG 4-1-2 Strip Entry 1

FIG 4-1-3 Strip Entry 2

f.

Flight progress strip item and information (see TBL 4-1-4).

TBL 4-1-4 Item and Information

ItemInformation
1Aircraft identification. To identify IFR aircraft piloted by solo U.S. Air Force undergraduate pilot, the letter `Z' will be added to aircraft ID on the flight progress strip. Do not use the suffix in ground-to-air communications.
2Type of aircraft/special equipment.
3True airspeed (TAS) and altitude (IFR). Altitude (VFR/DVFR, if known).
4Departure point.
5Route of flight.
6Destination.
7Actual departure time, or time VFR flight plan activated.
8ETA at destination.
9Estimated time of fuel exhaustion.
10Type of flight.
11Action time (for example, overdue time, fuel exhaustion time, LR contact time).
12Time of contact with pilot.
13Information received from pilot/another facility.
14Data issued to the aircraft.
g.

Flight progress strip abbreviations (see TBL 4-1-5).

TBL 4-1-5 Flight Progress Strip Abbreviations

AbbreviationMeaning
ÕOver flight
↓Inbound flight
↑Outbound flight
AAIRMET or G-AIRMET
AAAirport advisory
CWTCaution wake turbulence
DDVFR
DADecided against flight
DDDecided to delay flight
DWDownwind
FPFiled flight plan
IIFR
ICIncomplete briefing
PBPilot brief
RYRunway
SSVFR
VVFR
VNRVFR flight not recommended (pilot brief)
WSSIGMET
WSTConvective SIGMET
h.

Record ATC instructions and clearances completely and exactly.

i.

Summarize other data using approved symbols and contractions. See FIG 4-1-4 and FIG 4-1-5.

j.

Do not record issuance of altimeter setting unless that is the only information provided during the contact.

FIG 4-1-4 Control Information Symbols Chart 1

FIG 4-1-5 Control Information Symbols Chart 2

Referenced in This Section

JO 7110.10 2-5-3
Previous Section3-5 International SARNext Section 4-2 Radio Communications

You Are Reading

4-1-1 DESCRIPTION

Read Citation (on FlightPush)