|
Briefing Guide - Basic
Table of Contents
|
Paragraph
Number
|
Title
|
|
1-2-1
|
WORD MEANINGS
|
|
1-2-6
|
ABBREVIATIONS
|
|
2-1-28
|
RVSM OPERATIONS
|
|
2-7-2
|
ALTIMETER SETTING ISSUANCE
BELOW LOWEST USABLE FL
|
|
3-7-1
|
GROUND TRAFFIC MOVEMENT
|
|
3-9-1
|
DEPARTURE INFORMATION
|
|
3-9-9
|
TAKEOFF CLEARANCE
|
|
3-10-5
|
LANDING CLEARANCE
|
|
4-2-5
|
ROUTE OR ALTITUDE AMENDMENTS
|
|
4-5-7
|
ALTITUDE INFORMATION
|
|
9-2-9
|
SPECIAL INTEREST SITES
|
|
9-2-10
|
LAND-BASED AIR DEFENSE
IDENTIFICATION ZONE (ADIZ)/AIR TRAFFIC CONTROL (ATC) SECURITY SERVICES
|
|
9-8-1
|
General
|
1.
PARAGRAPH NUMBER AND TITLE: 1-2-1. WORD MEANINGS
2. BACKGROUND:
The Federal Aviation Administration (FAA) issued Order 1000.36, FAA Writing
Standards, to ensure that plain language standards apply to all FAA-written
documents. Plain language standards use “must” as a word of requirement
(indicating that an action is mandatory) rather than the word “shall,” which is
more ambiguous, regularly misused, breeds litigation, and is not used in common
speech. Throughout the Air Traffic Directives (such as FAA Order JO 7110.65 and
FAA Order JO 7210.3), both “must” and “shall” are used, though “must” is not
currently defined. This DCP adds the definition of “must” and clarifies word
usage. Additional information on “must versus shall” and plain language benefits
are available at http://www.plainlanguage.gov.
3. CHANGE:
|
OLD
|
|
NEW
|
|
1-2-1. WORD MEANINGS
|
|
1-2-1. WORD MEANINGS
|
|
As used in this manual:
|
|
As used in this
order:
|
|
a. Shall,
or an action verb in the imperative sense, means a procedure is
mandatory.
|
|
a. “Shall”
or “must” means a procedure is mandatory.
|
|
EXAMPLE-
|
|
Delete
|
|
Add
|
|
b. “Shall not” or
“must not” means a procedure is prohibited.
|
|
b through
g
|
|
Renumber c
thru h
|
|
h.
Approved separation means separation in accordance with the applicable
minima in this
manual.
|
|
i. “Approved
separation” means separation in accordance with the applicable minima in
this
order.
|
|
i through
o
|
|
Renumber j
through p
|
1. PARAGRAPH NUMBER
AND TITLE: 1-2-6. ABBREVIATIONS, and 9-8-1. General
2. BACKGROUND:
Bigelow Aerospace Advanced Space Studies (BAASS) is a new organization that is
devoted to exploration of extremely advanced aerospace technology, including the
so-called unidentified aerial phenomena (UAP) or unidentified flying object
(UFO) topics. In 2001, another of Mr. Bigelow's organizations, the National
Institute for Discovery Sciences (NIDS), succeeded in becoming the “go-to”
organization for the reporting by pilots and air traffic control of UFOs in the
United States. NIDS is now defunct and has been replaced by the larger, more
capable BAASS. Therefore, pilot and air traffic control reporting of UFOs in the
United States should now go to BAASS, vice NIDS. So we are deleting the NIDS
acronym and adding the BAASS acronym.
3. CHANGE:
|
OLD
|
NEW
|
|
TBL
1-2-1
FAA Order JO 7110.65 Abbreviations
|
TBL
1-2-1
FAA Order JO 7110.65 Abbreviations
|
|
|
|
|
|
|
|
|
|
|
Abbreviation
|
Meaning
|
|
Abbreviation
|
Meaning
|
|
|
|
Add
|
Add
|
|
BAASS
|
Bigelow Aerospace
Advanced Space Studies
|
|
|
|
NIDS
|
National Institute of
Discovery Sciences
|
|
Delete
|
Delete
|
|
|
|
|
|
|
|
|
|
|
OLD
|
|
NEW
|
|
9-8-1. GENERAL
|
|
9-8-1. GENERAL
|
|
a. Persons wanting
to report UFO/Unexplained
Phenomena activity should contact an UFO/Unexplained Phenomena
Reporting Data
Collection Center, such as the National Institute for Discovery
Sciences (NIDS), the National UFO Reporting Center, etc.
|
|
a. Persons wanting
to report UFO/unexplained
phenomena activity should contact a UFO/
unexplained phenomena reporting
data collection
center, such as Bigelow Aerospace Advanced Space Studies (BAASS)
(voice: 1-877-979-7444 or e-mail: Reporting@baass.org), the National UFO
Reporting Center, etc.
|
1. PARAGRAPH NUMBER AND
TITLE: 2-1-28. RVSM OPERATIONS
2. BACKGROUND: An
agreement was reached between the FAA and Department of Defense (DOD) to include
DOD certified aircraft operated by U.S. Government agencies in the definition of
DOD Reduced Vertical Separation Minimum (RVSM) excepted aircraft. Service
providers need clarification and guidance on what a “DOD certified aircraft” is
so exceptions can be granted, as appropriate.
3. CHANGE:
|
OLD
|
|
NEW
|
|
2-1-28. RVSM OPERATIONS
|
|
2-1-28. RVSM OPERATIONS
|
|
title through a
|
|
No Change
|
|
1. Ensure non-RVSM
aircraft are not permitted in RVSM airspace unless they meet the criteria of
excepted aircraft and are previously approved by the operations supervisor/controller-in-charge
(CIC). The following aircraft are excepted: DOD, Lifeguard,
manufacturer aircraft being flown for development/certification, and Foreign
State aircraft. These exceptions are accommodated on a workload or
traffic-permitting basis.
|
|
1. Ensure non-RVSM
aircraft are not permitted in RVSM airspace unless they meet the criteria of
excepted aircraft and are previously approved by the operations supervisor/CIC.
The following aircraft are excepted: DOD, DOD certified aircraft operated
by NASA (T38, F15, F18, WB57, S3, and U2 aircraft only), Lifeguard,
manufacturer aircraft being flown for development/certification, and Foreign
State aircraft. These exceptions are accommodated on a workload or
traffic-permitting basis.
|
|
NOTE-
The operations supervisor/CIC is responsible for system acceptance of a non-RVSM
aircraft beyond the initial sector to sector coordination
following the pilot request to access the airspace. Operations supervisor/CIC
responsibilities are defined in FAA Order 7210.3, Chapter 6,
Section 9, Reduced Vertical Separation Minimum (RVSM).
|
|
NOTE-
The operations supervisor/CIC is responsible for system acceptance of a non-RVSM
aircraft beyond the initial sector-to-sector
coordination following the pilot request to access the airspace. Operations
supervisor/CIC responsibilities are defined in FAAO JO 7210.3,
Chapter 6, Section 9, Reduced Vertical Separation Minimum (RVSM).
|
1.
PARAGRAPH NUMBER AND TITLE: 2-7-2. ALTIMETER SETTING ISSUANCE BELOW LOWEST
USABLE FL
2. BACKGROUND:
Using phraseology that includes numbers for time and altimeter setting in the
same message is causing reported confusion. The new phraseology provides the
needed information and eliminates the transmission of two sets of numbers in the
same radio message.
3. CHANGE:
|
OLD
|
|
NEW
|
|
2-7-2. ALTIMETER SETTING
ISSUANCE BELOW LOWEST USABLE FL
|
|
2-7-2. ALTIMETER SETTING
ISSUANCE BELOW LOWEST USABLE FL
|
|
title through b
|
|
No Change
|
|
PHRASEOLOGY-
THE (facility name) (time of report if more than one hour old) ALTIMETER
(setting).
|
|
PHRASEOLOGY-
(If the altimeter is one hour old or less),
THE (facility name) ALTIMETER (setting).
or
(If the altimeter is more than one hour old),
THE (facility name) ALTIMETER (setting) MORE THAN ONE HOUR OLD.
|
1. PARAGRAPH NUMBER AND
TITLE: 3-7-1. GROUND TRAFFIC MOVEMENT
2. BACKGROUND:
During facility audits, Safety Evaluations has identified numerous “Does Not
Meet Requirements” regarding the issuance of clearances for vehicular traffic to
proceed on runways and taxiways. The operation identified by Safety Evaluation
is the practice of issuing an “all surface clearance” such as “the field is
yours,” “proceed as requested on all runways and taxiways,” or “cleared on all
runways and taxiways.” This notice establishes the requirement of issuing
specific instructions and maintaining positive control while authorizing
movement on a runway and/or taxiway. Additionally, this change proposal
incorporates clarification of “declared distances” by the airport service to
achieve certain airport design criteria.
3. CHANGE:
|
OLD
|
|
NEW
|
|
3-7-1. GROUND TRAFFIC
MOVEMENT
|
|
3-7-1. GROUND TRAFFIC
MOVEMENT
|
|
title through a
|
|
No Change
|
|
Add
|
|
b. Do not issue
unconditional instructions when authorizing movement on a runway/taxiway for
the purpose of airfield checks or other airport operations. Instructions must
ensure positive control with specific instructions to proceed on a runway or
movement area, and as necessary, hold short instructions.
|
|
Add
|
|
REFERENCE-
FAAO JO 7110.65, Para 3-1-3, USE OF ACTIVE RUNWAYS
FAAO JO 7110.65, Para 3-7-2, TAXI AND GROUND MOVEMENT OPERATIONS
|
|
Add
|
|
EXAMPLE-
“Airport 1, proceed on Runway 26R, hold short of Runway 18L.”
“(Tower), Airport 1 at taxiway B8, request to inspect Runway 26R.” “Airport 1
proceed as requested, hold short of Runway 18L.”
“Airport 1 proceed on taxi way B, hold short of Runway 18L.”
|
|
Add
|
|
NOTE-
The following are examples of unconditional instructions and are not approved
for use: “THE FIELD IS YOURS,” “CLEARED ON ALL SURFACES,” “THE AIRPORT IS
YOURS,” and “PROCEED ON ALL RUNWAYS AND TAXIWAYS.”
|
|
b and
c
|
|
Renumber c
and d
|
|
NOTE-
Exceptions are authorized where specific military aircraft routinely make
intersection takeoffs and procedures are defined in appropriate directives. The
authority exercising operational control of such aircraft ensures that all
pilots are thoroughly familiar with these procedures, including the usable
runway length from the applicable intersection.
|
|
NOTE-
1. Exceptions are authorized where specific military aircraft
routinely make intersection takeoffs and procedures are defined in appropriate
directives. The authority exercising operational control of such aircraft
ensures that all pilots are thoroughly familiar with these procedures, including
the usable runway length from the applicable intersection.
|
|
Add
|
|
2. Some airports
publish “declared distances” for a particular runway. These are published in the
Airport Facility Directory (A/FD) or the Aeronautical Information Publication (AIP)
and there is no requirement that facility personnel be aware of them. These
distances are a means of satisfying airport design criteria and are intended to
be used by pilots and/or operators for preflight performance planning only.
There are no special markings, signing, or lighting associated with declared
distances and they do not limit the actual runway available for use by an
aircraft. Therefore, they cannot be used for any air traffic control purpose. If
pilots inquire about the existence of declared distances, refer them to the A/FD
or AIP.
|
|
d and
e
|
|
Renumber e
and f
|
1. PARAGRAPH NUMBER AND
TITLE: 3-9-1. DEPARTURE INFORMATION
2. BACKGROUND: In
May 2008, the FAA issued N JO 7110.482 (Taxi and Ground Movement Operations)
that mandated specific phraseology/procedures for the movement of
aircraft/vehicles on the movement area.
3. CHANGE:
|
OLD
|
|
NEW
|
|
3-9-1. DEPARTURE
INFORMATION
|
|
3-9-1. DEPARTURE
INFORMATION
|
|
title through d
|
|
No Change
|
|
e. Taxi
information, as necessary. You need not issue taxi route information unless the
pilot specifically requests it.
|
|
e. Issue the route
for the aircraft/vehicle to follow on the movement area in concise and easy to
understand terms. The taxi clearance must include the specific route to follow.
|
1. PARAGRAPH NUMBER AND
TITLE: 3-9-9. TAKEOFF CLEARANCE
2. BACKGROUND:
The Federal Aviation Administrators Call to Action Workgroup made numerous
recommendations to enhance runway safety. ATO-T Safety and Operations Support
assembled a Safety Risk Management (SRM) Panel to address some of the proposals
from this workgroup. This change provides a requirement for controllers when a
takeoff clearance can be issued. The panel did a safety assessment on takeoff
procedures at tower controlled airports and found no high risks associated with
this change.
Also, HQ Air Force Flight Standards Agency (AFFSA) requires all controllers to
issue wind speed and direction in conjunction with a takeoff clearance. The
requirement for the USAF to issue wind with a takeoff clearance is not
identified in the current FAA order.
3. CHANGE:
|
OLD
|
|
NEW
|
|
3-9-9. TAKEOFF CLEARANCE
|
|
3-9-9. TAKEOFF CLEARANCE
|
|
title through a
|
|
No Change
|
|
b. The controller
shall ensure that all runways along the taxi route that lead to the
departure runway are crossed before the takeoff clearance is issued, except
in subpara c.
|
|
b. The controller
must ensure that all runways along the taxi route that lead to the
departure runway are crossed before the takeoff clearance is issued, except
as stated in para 3-9-9c.
|
|
PHRASEOLOGY-
CROSS RUNWAY (number), RUNWAY (number) CLEARED FOR TAKEOFF.
|
|
Delete
|
|
EXAMPLE-
“CROSS RUNWAY TWO FOUR LEFT, RUNWAY TWO FOUR RIGHT, CLEARED FOR TAKEOFF.”
|
|
Delete
|
|
Add relocated
FIG 3-9-12
|
|
FIG
3-9-12
Runway/Taxiway Proximity
|
|
c
|
|
No Change
|
|
Add
|
|
PHRASEOLOGY-
CROSS RUNWAY (number), RUNWAY (number) CLEARED FOR TAKEOFF.
|
|
Add
|
|
EXAMPLE-
“CROSS RUNWAY TWO FOUR LEFT, RUNWAY TWO FOUR RIGHT, CLEARED FOR TAKEOFF.”
|
|
FIG
3-9-13
Runway/Taxiway Proximity
|
|
No Change
|
|
REFERENCE-
FAAO JO 7210.3, Para 10-3-9, Takeoff Clearance.
P/CG Term- Clear of the Runway.
|
|
No Change
|
|
PHRASEOLOGY-
CROSS RUNWAY (number), RUNWAY (number) CLEARED FOR TAKEOFF.
|
|
Delete
|
|
EXAMPLE-
“CROSS RUNWAY ONE SIX LEFT, RUNWAY ONE SIX RIGHT, CLEARED FOR TAKEOFF.”
|
|
Delete
|
|
d
|
|
No Change
|
|
e. USA/USN. Issue
surface wind and takeoff clearance to aircraft.
|
|
e. USA/USN/USAF.
Issue surface wind and takeoff clearance to aircraft.
|
|
PHRASEOLOGY-
WIND (surface wind in direction and velocity). CLEARED FOR TAKEOFF.
|
|
PHRASEOLOGY-
RUNWAY (number), WIND (surface wind in direction and velocity).
CLEARED FOR TAKEOFF.
|
1. PARAGRAPH NUMBER AND
TITLE: 3-10-5. LANDING CLEARANCE
2. BACKGROUND: HQ
Air Force Flight Standards Agency (AFFSA) requires all controllers to issue
runway identifier information along with wind speed and direction in conjunction
with all landing clearances. The requirement for the USAF to issue wind
information in conjunction with a landing clearance is not identified in the
current FAA order.
3. CHANGE:
|
OLD
|
|
NEW
|
|
3-10-5. LANDING CLEARANCE
|
|
3-10-5. LANDING CLEARANCE
|
|
title through d
EXAMPLE-
|
|
No Change
|
|
e. USA/USN.
Issue surface wind when clearing an aircraft to land, touch-and-go, stop-and-go,
low approach, or the option. Restate the landing runway whenever there is a
possibility of a conflict with another aircraft which is using or is planning to
use another runway.
|
|
e. USA/USN/USAF.
Issue runway identifier along with surface wind when clearing an
aircraft to land, touch and go, stop and go, low approach, or the option.
|
|
PHRASEOLOGY-
WIND (surface wind direction and velocity), CLEARED TO LAND,
or
WIND (surface wind direction and velocity), RUNWAY (designator) CLEARED TO LAND.
|
|
PHRASEOLOGY-
RUNWAY (number), WIND (surface wind direction and velocity),
CLEARED TO LAND.
|
1. PARAGRAPH NUMBER AND
TITLE: 4-2-5. ROUTE OR ALTITUDE AMENDMENTS
2. BACKGROUND:
FAA Order 8260.46, Departure Procedure Program, has been revised to implement
recommended changes to current policy by the Aeronautical Charting Forum,
Departure Working Group concerning procedure source, charting, and database
coding when one or more altitudes (i.e., minimum altitudes for obstruction
clearance/design constraint and ATC) are required at the same fix. ATC SID speed
restrictions will be identified by placing (ATC) at the end of the stated
restriction; e.g., “Do not exceed 230 KIAS until passing BRAVO (ATC).” This will
indicate to the pilot and the controller that this restriction is for ATC
purposes and can be deleted by ATC. The absence of (ATC) at the end of a speed
restriction indicates that it is there to support a TERPS criteria design
constraint and CANNOT be modified or deleted by ATC. Although this chart
annotation is not new, concise ATC operational guidance had not been
established. Detailed information can be obtained from Agenda Item 07-01-274
from the Aeronautical Charting Forum - Instrument Procedures Group at:
http://www.faa.gov/about/office_org/headquarters_offices/avs/offices/afs/afs400/afs420/acfipg/open/media/Hist%2007-01-274.pdf
3.
CHANGE:
|
OLD
|
|
NEW
|
|
4-2-5. ROUTE OR ALTITUDE
AMENDMENTS
|
|
4-2-5. ROUTE OR ALTITUDE
AMENDMENTS
|
|
title through b
EXAMPLE-
|
|
No Change
|
|
NOTE-
Restating previously issued altitude to “maintain” is an amended clearance. If
altitude to “maintain” is changed or restated, whether prior to departure or
while airborne, and previously issued altitude restrictions are omitted,
altitude restrictions are canceled, including SID/FMSP/STAR altitude
restrictions if any.
|
|
NOTE-
1. Restating previously issued altitude to “maintain” is an
amended clearance. If altitude to “maintain” is changed or restated, whether
prior to departure or while airborne, and previously issued altitude
restrictions are omitted, altitude restrictions are canceled, including SID/FMSP/STAR/(ATC)
altitude restrictions if any.
|
|
Add
|
|
2. All crossing
altitudes and speed restrictions not annotated as (ATC) for STARs and DPs,
including SIDs and ODPs, are mandatory and cannot be canceled by ATC. ATC
altitude restrictions and/or speed restrictions annotated (ATC) may be canceled
by ATC. In the event of lost communications, aircraft are expected to comply
with all restrictions unless ATC has previously canceled the ATC annotated
restrictions.
|
1. PARAGRAPH NUMBER AND
TITLE: 4-5-7. ALTITUDE INFORMATION
2. BACKGROUND:
This change supports an operating practice which has been safely in use for
years.
3. CHANGE:
|
OLD
|
|
NEW
|
|
4-5-7. ALTITUDE
INFORMATION
|
|
4-5-7. ALTITUDE
INFORMATION
|
|
title through b
PHRASEOLOGY-
|
|
No Change
|
|
c. Specified
altitude over a specified fix, waypoint.
|
|
c. Specified
altitude for crossing a specified fix
or waypoint; or, specified altitude for crossing a distance
(in miles) and direction from a specified fix or waypoint.
|
|
PHRASEOLOGY-
CROSS (fix, waypoint) AT (altitude).
CROSS (fix, waypoint) AT OR ABOVE/BELOW (altitude).
|
|
PHRASEOLOGY-
CROSS (fix, waypoint) AT (altitude).
CROSS (fix, waypoint) AT OR ABOVE/BELOW (altitude).
CROSS (number of miles) MILES (direction) OF (name of fix, waypoint) AT
(altitude).
CROSS (number of miles) MILES (direction) OF (name of fix, waypoint) AT OR
ABOVE/BELOW (altitude).
|
1.
PARAGRAPH NUMBER AND TITLE: 9-2-9. SPECIAL INTEREST SITES
2. BACKGROUND:
All security related events or suspected security related events must be
reported to the Domestic Events Network (DEN).
3. CHANGE:
|
OLD
|
|
NEW
|
|
9-2-9. SPECIAL INTEREST
SITES
|
|
9-2-9. SPECIAL INTEREST
SITES
|
|
title through b
|
|
No Change
|
|
c. ARTCCs shall
promptly advise the ATCSCC of any actions taken in accordance with this
paragraph.
|
|
c. ARTCCs shall
promptly advise the Domestic Events Network (DEN) of any actions
taken in accordance with this paragraph.
|
1. PARAGRAPH NUMBER AND
TITLE: 9-2-10. LAND-BASED AIR DEFENSE IDENTIFICATION ZONE (ADIZ)/AIR TRAFFIC
CONTROL (ATC) SECURITY SERVICES
2. BACKGROUND: On
Febuary 17, 2009, the Washington DC ADIZ was changed by rulemaking to the
Special Flight Rules Area (SFRA). The procedures that will be used for the SFRA
are the same as for a land based ADIZ. Additionally, since Washington ARTCC may
have to assume the airspace if Potomac TRACON went ATC-0, the reference to
Terminal was deleted.
3. CHANGE:
|
OLD
|
|
NEW
|
|
9-2-10. LAND-BASED AIR
DEFENSE IDENTIFICATION ZONE (ADIZ)/AIR TRAFFIC CONTROL (ATC)
SECURITY SERVICES
|
|
9-2-10. WASHINGTON, DC,
SPECIAL FLIGHT RULES AREA (DC SFRA)/ATC SECURITY SERVICES
|
|
TERMINAL
|
|
Delete
|
|
Provide ATC security
services at locations where procedures are required for the tracking
of aircraft in security services airspace. ATC security services are
designed to support the national security mission of the FAA and other agencies.
Two-way radio communications, flight planning, and operational transponder on an
assigned code are required for operations within the designated area.
|
|
Provide ATC security
services at locations where procedures are required for tracking aircraft in
security services airspace. ATC security services are designed to support the
national security mission of the FAA and other agencies. Two-way radio
communications, flight planning, and an operational transponder on an assigned
code are required for operations in the designated area.
|
|
a through aPHRASEOLOGY-
|
|
No Change
|
|
1. Maintain
continuous security tracking of VFR aircraft operating within the
designated area to assist security forces in situational awareness. Immediately
report all instances of loss of radio communication or the inability to conduct
security tracking of an aircraft to the FLM/CIC and await instructions.
|
|
1. Maintain
continuous security tracking of VFR aircraft operating in the designated area to
assist security forces in situational awareness. Immediately report all
instances of loss of radio communication or the inability to conduct security
tracking of an aircraft to the front line manager (FLM)/CIC
and wait for instructions.
|
|
2. The provision
of basic separation services to aircraft, i.e., IFR, SVFR, Class B,
Class C, TRSA,
is not applicable to ATC security tracking.
|
|
2. Basic
separation services to aircraft, for example, IFR, SVFR, Class B,
Class C, TRSA, do not apply to ATC security
tracking.
|
|
3. Aircraft with
operating transponders, but without operating Mode C (altitude) require specific
authorization from ATC in order to operate
within the ADIZ. ATC must coordinate with the Domestic Events
Network (DEN) prior to approval.
|
|
3. Aircraft with
operating transponders, but without operating Mode C (altitude),
require specific authorization from ATC to operate in the
SFRA. ATC must coordinate with the Domestic Events Network (DEN)
before approval.
|
|
4. Aircraft flying
too low for radar coverage
shall be instructed to report landing or exiting the
ADIZ. Maintain flight progress strips on such aircraft
until pilot reports landing or exiting the
ADIZ. If a flight progress strip does not exist for the aircraft, record
the call sign, transponder code, entry point (e.g., north, northeast,
east), and time of entry into the ADIZ.
|
|
4. Aircraft flying
too low for radar coverage
must be instructed to report landing or exiting the
SFRA. Keep flight progress strips on these
aircraft until pilot reports landing or exiting the SFRA. If a
flight progress strip does not exist for the aircraft, record the call sign,
transponder code, entry point (for example, north, northeast,
east), and time of entry into the SFRA.
|
|
PHRASEOLOGY-
(Call sign), REPORT LANDING OR LEAVING THE
ADIZ.
|
|
PHRASEOLOGY-
(Call sign), REPORT LANDING OR LEAVING THE
SFRA.
|
|
5. United States
Military, law enforcement, and aeromedical flights are exempt from filing
flight plans.
|
|
5. United States
military, law enforcement, and aeromedical flights are exempt from
filing flight plans.
|
|
b. Establishing
Two-Way Communications.
|
|
b. Establishing
two-way communications.
|
|