- 注册时间
- 2008-9-13
- 最后登录
- 1970-1-1
- 在线时间
- 0 小时
- 阅读权限
- 200
- 积分
- 0
- 帖子
- 24482
- 精华
- 4
- UID
- 9
|
6.4.3_Flights in a Radar Environment. When
informed by ATC that their aircraft are in _RADAR
CONTACT," PILOTS SHOULD DISCONTINUE
POSITION REPORTS OVER DESIGNATED RE-
PORTING POINTS. They should resume normal
position reporting when ATC advises _RADAR
CONTACT LOST" or _RADAR SERVICE TERMI-
NATED."
NOTE-
ATC will inform pilots that they are in _radar contact"
(a)_When their aircraft is initially identified in the ATC
system; and (b) When radar identification is reestablished
after radar service has been terminated or radar contact
has been lost. Subsequent to being advised that the
controller has established radar contact, this fact will not
be repeated to the pilot when handed off to another
controller. At times, the aircraft identity will be confirmed
by the receiving controller; however, this should not be
construed to mean that radar contact has been lost. The
identity of transponder-equipped aircraft will be
confirmed by asking the pilot to _ident, squawk standby,"
or to change codes. Aircraft without transponders will be
advised of their position to confirm identity. In this case, the
pilot is expected to advise the controller if in disagreement
with the position given. If the pilot cannot confirm the
accuracy of the position given because of not being tuned
to the NAVAID referenced by the controller, the pilot should
ask for another radar position relative to the tuned in
NAVAID.
6.5_Position Report Items
6.5.1_Position reports should include the following items:
6.5.1.1_Identification.
6.5.1.2_Position.
6.5.1.3_Time.
6.5.1.4_Altitude or flight level (Include actual
altitude or flight level when operating on a clearance
specifying _VFR-on-top.").
6.5.1.5_Type of flight plan (not required in IFR
position reports made directly to ARTCCs or
approach control).
6.5.1.6_ETA and name of next reporting point.
6.5.1.7_The name only of the next succeeding
reporting point along the route of flight.
6.5.1.8_Pertinent remarks.
7. Additional Reports
7.1_The following reports should be made to ATC or
FSS facilities without a specific request:
7.1.1_At all times, report:
7.1.1.1_When vacating any previously assigned
altitude/flight level for a newly assigned altitude/
flight level.
7.1.1.2_When an altitude change will be made if
operating on a clearance specifying _VFR-on-top."
7.1.1.3_When unable to climb/descend at a rate of at
least 500 feet per minute.
7.1.1.4_When approach has been missed. (Request
clearance for specific action; i.e., to alternative
airport, another approach, etc.).
7.1.1.5_Change in the average true airspeed (at
cruising altitude) when it varies by 5 percent or
10_knots (whichever is greater) from that filed in the
flight plan.
7.1.1.6_The time and altitude/flight level reaching a
holding fix or point to which cleared.
7.1.1.7_When leaving any assigned holding fix or
point.
NOTE-
The reports in subparagraphs 7.1.1.6 and 7.1.1.7 may be
omitted by pilots of aircraft involved in instrument training
at military area facilities when radar service is being
provided.
7.1.1.8_Any loss, in controlled airspace, of VOR,
TACAN, ADF, low frequency navigation receiver
capability, GPS anomalies while using installed
IFR-certified GPS/GNSS receivers, complete or
partial loss of ILS receiver capability or impairment
of air/ground communications capability. Reports
should include aircraft identification, equipment
affected, degree to which the capability to operate
under IFR in the ATC system is impaired, and the
nature and extent of assistance desired from ATC.
NOTE-
When reporting GPS anomalies, include the location and
altitude of the anomaly. Be specific when describing the
location and include duration of the anomaly if necessary.
7.1.1.9_Any information relating to the safety of
flight.
AIP
United States of America
GEN 3.3-6
15 MAR 07
Federal Aviation Administration Nineteenth Edition
NOTE-
Other equipment installed in an aircraft may effectively
impair safety and/or the ability to operate under IFR. If
such equipment; e.g., airborne weather radar, malfunctions and in the pilot’s judgment either safety or IFR
capabilities are affected, reports should be made as above.
7.2_When not in radar contact, report:
7.2.1_When leaving the final approach fix inbound
on final approach (nonprecision approach) or when
leaving the outer marker or fix used in lieu of the outer
marker inbound on final approach (precision
approach); or
7.2.2_A corrected estimate at any time it becomes
apparent that an estimate as previously submitted is
in error in excess of 3 minutes.
7.3_Pilots encountering weather conditions which
have not been forecast, or hazardous conditions
which have been forecast, are expected to forward a
report of such weather to ATC.
8. Quota Flow Control
8.1_Quota Flow Control is designed to balance the
ATC system demand with system capacity.
8.2_ARTCCs will hold the optimum number of
aircraft that their primary and secondary holding
fixes will safely accommodate without imposing
undue limitations on the control of other traffic
operating within the ARTCC’s airspace. This is based
on the user’s requirement to continue operating to a
terminal regardless of the acceptance rate at that
terminal. When staffing, equipment, or severe
weather will inhibit the number of aircraft the arrival
ARTCC may safely hold, a reduction may be
necessary.
8.3_When an ARTCC is holding the optimum
number of aircraft, the adjacent ARTCCs will be
issued quotas concerning aircraft which can be
cleared into the impacted ARTCC’s airspace. When
the adjacent center’s demand exceeds the quota,
aircraft will be held in the adjacent ARTCC’s airspace
until they can be permitted to proceed.
8.4_The size of the hourly quota will be based
initially on the projected acceptance rate and
thereafter on the actual landing and diversion totals.
Once quotas have been imposed, departures in the
arrival and adjacent ARTCC’s area to the affected
airport may be assigned ground delay, if necessary, to
limit airborne holding to ATC capacity. However,
when a forecast of improved acceptance rate appears
reliable, in the opinion of the arrival ARTCC,
additional above-quota flights may be approved
based on the expectation that by the time these
additional above-quota flights become an operational factor in the affected area, the system will be able
to absorb them without undue difficulty.
8.5_Long distance flights, which originate beyond
the adjacent ARTCC area, will normally be permitted
to proceed to a point just short of the arrival ARTCC
boundary where a delay, at least equal to the delays
(ground/airborne) being encountered, will be assigned.
8.6_ARTCCs imposing ground delays make efforts
to advise the users when lengthy delays are a prospect
to preclude unnecessary boarding and subsequent
unloading prior to actual takeoff due to lengthy
unanticipated ground delays. Users should advise the
ARTCC through FSS or operation offices when there
is any significant change in the proposed departure
time so as to permit more efficient flow control
planning. Airborne aircraft holding in the adjacent
ARTCC airspace generally receive more benefit than
ground delayed aircraft when increases unexpectedly
develop in the quota number because the reaction
time is less. For this reason, whenever operationally
feasible, adjacent ARTCCs may offer airborne delay
within their areas instead of ground delay.
8.7_Flights originating beyond the adjacent ARTCC
areas may not have sufficient fuel to absorb the total
anticipated delay while airborne. Accordingly, the
concerned adjacent ARTCC may permit these flights
to land in its area while retaining previously
accumulated delay for the purpose of quota priority.
When the amount of air traffic backlogging in an
adjacent ARTCC area is approaching the saturation
point, additional en route traffic will be subject to
prior approval.
8.8_Generally, movement of arrival aircraft into the
impacted airport terminal area will be made on the
basis that those flights with the most accumulated
delay, either ground, airborne, or a combination of
both, normally receive priority over other traffic. This
applies only to delays encountered because of the
situation at the airport of intended landing.
8.9_Pilots/operators are advised to check for flow
control advisories which are transmitted to FSSs, to
selected airline dispatch offices, and to ARTCCs.
AIP
United States of America
GEN 3.3-7
15 MAR 07
Federal Aviation Administration Nineteenth Edition
9. Advisory and Air Traffic Information
Services
9.1 Approach Control Service for VFR Arriving
Aircraft
9.1.1 Numerous approach control facilities have
established programs for arriving VFR aircraft to
contact approach control for landing information.
This information includes: wind, runway, and
altimeter setting at the airport of intended landing.
This information may be omitted if contained in the
ATIS broadcast and the pilot states the appropriate
ATIS code.
NOTE-
Pilot use of “have numbers” does not indicate receipt of the
ATIS broadcast. In addition, the controller will provide
traffic advisories on a workload permitting basis.
9.1.2 Such information will be furnished upon initial
contact with the concerned approach control facility.
The pilot will be requested to change to the tower
frequency at a predetermined time or point, to receive
further landing information.
9.1.3 Where available, use of this procedure will not
hinder the operation of VFR flights by requiring
excessive spacing between aircraft or devious
routing. Radio contact points will be based on time or
distance rather than on landmarks.
9.1.4 Compliance with this procedure is not
mandatory, but pilot participation is encouraged. (See
ENR 1.1, paragraph 39, Terminal Radar Services for
VFR Aircraft.)
NOTE-
Approach control services for VFR aircraft are normally
dependent on air traffic control radar. These services are
not available during periods of a radar outage. Approach
control services for VFR aircraft are limited when Center
Radar ARTS Presentation/ Processing (CENRAP) is in
use.
9.2 Traffic Advisory Practices at Airports
Without Operating Control Towers
9.2.1 Airport Operations Without an Operating
Control Tower
9.2.1.1 There is no substitute for alertness while in
the vicinity of an airport. It is essential that pilots be
alert and look for other traffic and exchange traffic
information when approaching or departing an
airport without an operating control tower. This is of
particular importance since other aircraft may not
have communication capability or, in some cases,
pilots may not communicate their presence or
intentions when operating into or out of such airports.
To achieve the greatest degree of safety, it is essential
that all radio-equipped aircraft transmit/receive on a
common frequency identified for the purpose of
airport advisories.
9.2.1.2 An airport may have a full or part-time tower
or FSS located on the airport, a full or part-time
UNICOM station or no aeronautical station at all.
There are three ways for pilots to communicate their
intention and obtain airport/traffic information when
operating at an airport that does not have an operating
tower: by communicating with an FSS, a UNICOM
operator, or by making a self-announce broadcast.
9.2.1.3 Many airports are now providing completely
automated weather, radio check capability and airport
advisory information on an automated UNICOM
system. These systems offer a variety of features,
typically selectable by microphone clicks, on the
UNICOM frequency. Availability of the automated
UNICOM will be published in the Airport/Facility
Directory and approach charts.
9.2.2 Communicating on a Common Frequency
9.2.2.1 The key to communicating at an airport
without an operating control tower is selection of the
correct common frequency. The acronym, CTAF,
which stands for common traffic advisory frequency,
is synonymous with this program. A CTAF is a
frequency designated for the purpose of carrying out
airport advisory practices while operating to or from
an airport without an operating control tower. The
CTAF may be a UNICOM, MULTICOM, FSS, or
tower frequency and is identified in appropriate
aeronautical publications.
9.2.2.2 The CTAF frequency for a particular airport
is contained in the Airport/Facility Directory (A/FD),
Alaska Supplement, Alaska Terminal Publication,
Instrument Approach Procedure Charts, and Instrument Departure Procedure (DP) charts. Also, the
CTAF frequency can be obtained by contacting any
FSS. Use of the appropriate CTAF, combined with a
visual alertness and application of the following
recommended good operating practices, will enhance
safety of flight into and out of all uncontrolled
airports.
AIP
United States of America
GEN 3.3-8
15 MAR 07
Federal Aviation Administration Nineteenth Edition
9.2.3 Recommended Traffic Advisory Practices
9.2.3.1 Pilots of inbound aircraft should monitor and
communicate on the designated CTAF from 10 miles
to landing. Pilots of departing aircraft should
monitor/communicate on the appropriate frequency
from start-up, during taxi, and until 10 miles from the
airport unless the Code of Federal Regulations (CFR)
or local procedures require otherwise.
9.2.3.2 Pilots of aircraft conducting other than
arriving or departing operations at altitudes normally
used by arriving and departing aircraft should
monitor/communicate on the appropriate frequency
while within 10 miles of the airport unless required to
do otherwise by the CFR or local procedures. Such
operations include parachute jumping/dropping (see
ENR 5.1, paragraph 2.3, Parachute Jump Aircraft
Operations), en route, practicing maneuvers, etc.
9.2.4 Airport Advisory/Information Services
Provided by a FSS
9.2.4.1 There are three advisory type services
provided at selected airports.
a) Local Airport Advisory (LAA) is provided at
airports that have a FSS physically located on the
airport, which does not have a control tower or where
the tower is operated on a part-time basis. The CTAF
for LAA airports is disseminated in the appropriate
aeronautical publications.
b) Remote Airport Advisory (RAA) is provided at
selected very busy GA airports, which do not have an
operating control tower. The CTAF for RAA airports
is disseminated in the appropriate aeronautical
publications. Hours of operation may be changed by
NOTAM D.
c) Remote Airport Information Service (RAIS) is
provided in support of special events at nontowered
airports by request from the airport authority and
shall be published as a NOTAM D.
9.2.4.2 In communicating with a CTAF FSS, check
the airport’s automated weather and establish
two-way communications before transmitting outbound/inbound intentions or information. An inbound aircraft should initiate contact approximately
10 miles from the airport, reporting aircraft
identification and type, altitude, location relative to
the airport, intentions (landing or over flight),
possession of the automated weather, and request
airport advisory or airport information service. A
departing aircraft should initiate contact before
taxiing, reporting aircraft identification and type,
VFR or IFR, location on the airport, intentions,
direction of take-off, possession of the automated
weather, and request airport advisory or information
service, as applicable. Also, report intentions before
taxiing onto the active runway for departure. If you
must change frequencies for other service after initial
report to FSS, return to FSS frequency for traffic
update.
a) Inbound
EXAMPLE-
Vero Beach radio, Centurion Six Niner Delta Delta is ten
miles south, two thousand, landing Vero Beach. I have the
automated weather, request airport advisory.
b) Outbound
EXAMPLE-
Vero Beach radio, Centurion Six Niner Delta Delta, ready
to taxi to runway 22, VFR, departing to the southwest. I
have the automated weather, request airport advisory.
9.2.4.3 Airport advisory service includes wind
direction and velocity, favored or designated runway,
altimeter setting, known airborne and ground traffic,
NOTAMs, airport taxi routes, airport traffic pattern
information, and instrument approach procedures.
These elements are varied so as to best serve the
current traffic situation. Some airport managers have
specified that under certain wind or other conditions
designated runways be used. Pilots should advise the
FSS of the runway they intend to use.
9.2.4.4 Automatic Flight Information Service
(AFIS) -Alaska FSSs Only
9.2.4.4.1 Alaska FSSs AFIS is the continuous
broadcast of recorded noncontrol information at
airports in Alaska where a Flight Service Station
(FSS) provides local airport advisory service. Its
purpose is to improve FSS Specialist efficiency by
reducing frequency congestion on the local airport
advisory frequency. The AFIS broadcast will
automate the repetitive transmission of essential but
routine information (weather, favored runway,
breaking action, airport NOTAMs, other applicable
information). The information is continuously
broadcast over a discrete VHF radio frequency
(usually the ASOS frequency). Use of AFIS is not
mandatory, but pilots who choose to utilize two-way
radio communications with the FSS are urged to
listen to AFIS, as it relieves frequency congestion on
the local airport advisory frequency. AFIS
31 JULY 08
AIP
United States of America
GEN 3.3-9
15 MAR 07
Federal Aviation Administration Nineteenth Edition
broadcasts are updated upon the receipt of any
official hourly and special weather, worsening
braking action reports, and changes in other pertinent
data. When a pilot acknowledges receipt of the AFIS
broadcast, FSS Specialists may omit those items
contained in the broadcast if they are current. When
rapidly changing conditions exist, the latest ceiling,
visibility, altimeter, wind or other conditions may be
omitted from the AFIS and will be issued by the
Flight Service Specialist on the appropriate radio
frequency.
EXAMPLE-
“Kotzebue information ALPHA. One six five five zulu.
Wind, two one zero at five; visibility two, fog; ceiling one
hundred overcast; temperature minus one two, dew point
minus one four; altimeter three one zero five. Altimeter in
excess of three one zero zero, high pressure altimeter
setting procedures are in effect. Favored runway two six.
Weather in Kotzebue surface area is below V-F-R
minima -an ATC clearance is required. Contact
Kotzebue Radio on 123.6 for traffic advisories and advise
intentions. Notice to Airmen, Hotham NDB out of service.
Transcribed Weather Broadcast out of service. Advise on
initial contact you have ALPHA.”
NOTE-
The absence of a sky condition or ceiling and/or visibility
on Alaska FSS AFIS indicates a sky condition or ceiling of
5,000 feet or above and visibility of 5 miles or more. A
remark may be made on the broadcast, “the weather is
better than 5000 and 5.”
9.2.4.4.2 Pilots should listen to Alaska FSSs AFIS
broadcasts whenever Alaska FSSs AFIS is in
operation.
NOTE-
Some Alaska FSSs are open part time and/or seasonally.
9.2.4.4.3 Pilots should notify controllers on initial
contact that they have received the Alaska FSSs
AFIS broadcast by repeating the phonetic alphabetic
letter appended to the broadcast.
EXAMPLE-
“Information Alpha received.”
9.2.4.4.4 While it is a good operating practice for
pilots to make use of the Alaska FSS AFIS broadcast
where it is available, some pilots use the phrase “have
numbers” in communications with the FSS. Use of
this phrase means that the pilot has received wind,
runway, and altimeter information ONLY and the
Alaska FSS does not have to repeat this information.
It does not indicate receipt of the AFIS broadcast and
should never be used for this purpose.
CAUTION-
All aircraft in the vicinity of an airport may not be in
communication with the FSS.
9.2.5 Information Provided by Aeronautical
Advisory Stations (UNICOM)
9.2.5.1 UNICOM is a nongovernment air/ground
radio communication station which may provide
airport information at public use airports where there
is no tower or FSS.
9.2.5.2 On pilot request, UNICOM stations may
provide pilots with weather information, wind
direction, the recommended runway, or other
necessary information. If the UNICOM frequency is
designated as the CTAF, it will be identified in
appropriate aeronautical publications.
9.2.5.3 Unavailability of Information from FSS
or UNICOM. Should LAA by an FSS or
Aeronautical Advisory Station UNICOM be unavailable, wind and weather information may be
obtainable from nearby controlled airports via
Automatic Terminal Information Service (ATIS) or
Automated Weather Observing System (AWOS)
frequency.
9.2.6 Self-Announce Position and/or Intentions
9.2.6.1 General. Self-announce is a procedure
whereby pilots broadcast their position or intended
flight activity or ground operation on the designated
CTAF. This procedure is used primarily at airports
which do not have an FSS on the airport. The
self-announce procedure should also be used if a pilot
is unable to communicate with the FSS on the
designated CTAF. Pilots stating, “Traffic in the area,
please advise” is not a recognized Self-Announce
Position and/or Intention phrase and should not be
used under any condition.
9.2.6.2 If an airport has a tower which is temporarily
closed or operated on a part-time basis, and there is
no FSS on the airport or the FSS is closed, use the
CTAF to self-announce your position or intentions.
9.2.6.3 Where there is no tower, FSS, or UNICOM
station on the airport, use MULTICOM frequency
122.9 for self-announce procedures. Such airports
will be identified in appropriate aeronautical
information publications.
9.2.6.4 Practice Approaches. Pilots conducting
practice instrument approaches should be particularly alert for other aircraft that may be departing in the
opposite direction. When conducting any practice
31 JULY 08
AIP
United States of America
GEN 3.3-10
15 MAR 07
Federal Aviation Administration Nineteenth Edition
approach, regardless of its direction relative to other
airport operations, pilots should make announcements on the CTAF as follows:
a) Departing the final approach fix, inbound
(nonprecision approach) or departing the outer
marker or fix used in lieu of the outer marker, inbound
(precision approach).
b) Established on the final approach segment or
immediately upon being released by ATC.
c) Upon completion or termination of the
approach; and
d) Upon executing the missed approach procedure.
9.2.6.5 Departing aircraft should always be alert for
arrival aircraft coming from the opposite direction.
9.2.6.6 Recommended Self-Announce Phraseologies. It should be noted that aircraft operating to or
from another nearby airport may be making
self-announce broadcasts on the same UNICOM or
MULTICOM frequency. To help identify one airport
from another, the airport name should be spoken at
the beginning and end of each self-announce
transmission.
a) Inbound
EXAMPLE-
Strawn traffic, Apache Two Two Five Zulu, (position),
(altitude), (descending) or entering downwind/base/ final
(as appropriate) runway one seven full stop/touch-
and-go, Strawn.
Strawn traffic Apache Two Two Five Zulu clear of runway
one seven Strawn.
b) Outbound
EXAMPLE-
Strawn traffic, Queen Air Seven One Five Five Bravo
(location on airport) taxiing to runway two six Strawn.
Strawn traffic, Queen Air Seven One Five Five Bravo
departing runway two six. “Departing the pattern to the
(direction), climbing to (altitude) Strawn.”
c) Practice Instrument Approach
EXAMPLE-
Strawn traffic, Cessna Two One Four Three Quebec
(position from airport) inbound descending through
(altitude) practice (name of approach) approach runway
three five Strawn.
Strawn traffic, Cessna Two One Four Three Quebec
practice (type) approach completed or terminated runway
three five Strawn.
9.2.7 UNICOM Communication Procedures
9.2.7.1 In communicating with a UNICOM station,
the following practices will help reduce frequency
congestion, facilitate a better understanding of pilot
intentions, help identify the location of aircraft in the
traffic pattern, and enhance safety of flight:
a) Select the correct UNICOM frequency.
b) State the identification of the UNICOM station
you are calling in each transmission.
c) Speak slowly and distinctly.
d) Report approximately 10 miles from the
airport, reporting altitude, and state your aircraft type,
aircraft identification, location relative to the airport,
state whether landing or overflight, and request wind
information and runway in use.
e) Report on downwind, base and final approach.
f) Report leaving the runway.
9.2.7.2 Recommended UNICOM Phraseologies:
a) Inbound.
PHRASEOLOGY-
FREDERICK UNICOM CESSNA EIGHT ZERO ONE
TANGO FOXTROT 10 MILES SOUTHEAST DE-
SCENDING THROUGH (altitude) LANDING FREDER-
ICK, REQUEST WIND AND RUNWAY INFORMATION
FREDERICK.
FREDERICK TRAFFIC CESSNA EIGHT ZERO ONE
TANGO FOXTROT ENTERING DOWNWIND/BASE/
FINAL (as appropriate) FOR RUNWAY ONE NINER
FULL STOP/TOUCH-AND-GO FREDERICK.
FREDERICK TRAFFIC CESSNA EIGHT ZERO ONE
TANGO FOXTROT CLEAR OF RUNWAY ONE NINER
FREDERICK.
31 JULY 08
AIP
United States of America
GEN 3.3-11
15 MAR 07
Federal Aviation Administration Nineteenth Edition
b) Outbound
PHRASEOLOGY-
FREDERICK UNICOM CESSNA EIGHT ZERO ONE
TANGO FOXTROT (location on airport) TAXIING TO
RUNWAY ONE NINE, REQUEST WIND AND TRAFFIC
INFORMATION FREDERICK.
FREDERICK TRAFFIC CESSNA EIGHT ZERO ONE
TANGO FOXTROT DEPARTING RUNWAY ONE NINE.
“REMAINING IN THE PATTERN” OR “DEPARTING
THE PATTERN TO THE (direction) (as appropriate)”
FREDERICK.
9.3 IFR Approaches/Ground Vehicle Operations
9.3.1 IFR Approaches. When operating in accordance with an IFR clearance and ATC approves a
change to the advisory frequency, make an
expeditious change to the CTAF and employ the
recommended traffic advisory procedures.
9.3.2 Ground Vehicle Operation. Airport ground
vehicles equipped with radios should monitor the
CTAF frequency when operating on the airport
movement area and remain clear of runways/taxiways being used by aircraft. Radio transmissions
from ground vehicles should be confined to
safety-related matters.
9.3.3 Radio Control of Airport Lighting Systems.
Whenever possible, the CTAF will be used to control
airport lighting systems at airports without operating
control towers. This eliminates the need for pilots to
change frequencies to turn the lights on and allows a
continuous listening watch on a single frequency. The
CTAF is published on the instrument approach chart
and in other appropriate aeronautical information
publications. For further details concerning radio
controlled lights, see Advisory Circular 150/5340.27.
TBL GEN 3.3-1
Summary of Recommended Communication Procedures
COMMUNICATION/BROADCAST
PROCEDURES
Facility at
Airport
Frequency Use Outbound Inbound
Practice
Instrument
Approach
1. UNICOM (No
Tower or FSS)
Communicate with UNICOM
station on published CTAF
frequency (122.7; 122.8;
122.725; 122.975; or 123.0).
If unable to contact UNICOM
station, use self-announce
procedures on CTAF.
Before taxiing and
before taxiing
onto the runway
for departure.
10 miles out;
entering
downwind, base,
and final; leaving
the runway.
2. No Tower, FSS, or
UNICOM
Self-announce on
MULTICOM frequency
122.9.
Before taxiing and
before taxiing
onto the runway
for departure.
10 miles out;
entering
downwind, base,
and final; leaving
the runway.
Departing final
approach fix
(name) or on final
approach segment
inbound.
3. No Tower in
operation, FSS open
Communicate with FSS on
CTAF frequency.
Before taxiing and
before taxiing
onto the runway
for departure.
10 miles out;
entering
downwind, base,
and final; leaving
the runway.
Approach
completed/
terminated.
4. FSS closed
(No Tower)
Self-announce on CTAF. Before taxiing and
before taxiing
onto the runway
for departure.
10 miles out;
entering
downwind, base,
and final; leaving
the runway.
5. Tower or FSS not in
operation
Self-announce on CTAF. Before taxiing and
before taxiing
onto the runway
for departure.
10 miles out;
entering
downwind, base,
and final; leaving
the runway.
31 JULY 08
AIP
United States of America
GEN 3.3-12
15 MAR 07
Federal Aviation Administration Nineteenth Edition
9.4 Designated UNICOM/MULTICOM
Frequencies
9.4.1 Frequency Use
9.4.1.1 TBL GEN 3.3-2 depicts UNICOM and
MULTICOM frequency uses as designated by the
Federal Communications Commission (FCC).
NOTE-
1. In some areas of the country, frequency interference
may be encountered from nearby airports using the same
UNICOM frequency. Where there is a problem, UNICOM
operators are encouraged to develop a “least
interference” frequency assignment plan for airports
concerned using the frequencies designated for airports
without operating control towers. UNICOM licensees are
encouraged to apply for UNICOM 25 KHz spaced channel
frequencies. Due to the extremely limited number of
frequencies with 50 KHz channel spacing, 25 KHz channel
spacing should be implemented. UNICOM licensees may
then request FCC to assign frequencies in accordance with
the plan, which FCC will review and consider for approval.
2. Wind direction and runway information may not be
available on UNICOM frequency 122.950.
9.4.2.1 TBL GEN 3.3-3 depicts other frequency
uses as designated by the FCC.
9.5 Use of UNICOM for ATC purposes
9.5.1 UNICOM service may be used for air traffic
control purposes, only under the following circumstances:
9.5.1.1 Revision to proposed departure time.
9.5.1.2 Takeoff, arrival, or flight plan cancellation
time.
9.5.1.3 ATC clearance, provided arrangements are
made between the ATC facility and the UNICOM
licensee to handle such messages.
TBL GEN 3.3-2
UNICOM/MULTICOM Frequency Usage
Use Frequency
Airports without an
operating control tower.
122.700
122.725
122.800
122.975
123.000
123.050
123.075
(MULTICOM
FREQUENCY) Activities
of a temporary, seasonal,
emergency nature or
search and rescue, as well
as, airports with no tower,
FSS, or UNICOM.
122.900
(MULTICOM
FREQUENCY) Forestry
management and fire
suppression, fish and
game management and
protection, and
environmental monitoring
and protection.
122.925
Airports with a control
tower or FSS on airport.
122.950
TBL GEN 3.3-3
Other Frequency Usage Designated by FCC
Use Frequency
Air-to-air communication
(private fixed wing
aircraft).
122.750
Air-to-air communications
(general aviation
helicopters).
123.025
Aviation instruction,
Glider, Hot Air Balloon
(not to be used for
advisory service).
123.300
123.500
AIP
United States of America
GEN 3.3-13
15 MAR 07
Federal Aviation Administration Nineteenth Edition
9.6_Automatic Terminal Information Service
(ATIS)
9.6.1_ATIS is the continuous broadcast of recorded
noncontrol information in selected high activity
terminal areas. Its purpose is to improve controller
effectiveness and to relieve frequency congestion by
automating the repetitive transmission of essential
but routine information. The information is continuously broadcast over a discrete VHF radio frequency
or the voice portion of a local NAVAID. ATIS
transmissions on a discrete VHF radio frequency are
engineered to be receivable to a maximum of 60 NM
from the ATIS site and a maximum altitude of
25,000_feet AGL. At most locations, ATIS signals
may be received on the surface of the airport, but local
conditions may limit the maximum ATIS reception
distance and/or altitude. Pilots are urged to cooperate
in the ATIS program as it relieves frequency
congestion on approach control, ground control, and
local control frequencies. The Airport/Facility
Directory indicates airports for which ATIS is
provided.
9.6.2_ATIS information includes the time of the latest
weather sequence, ceiling, visibility, obstructions to
visibility, temperature, dew point (if available), wind
direction (magnetic), and velocity, altimeter, other
pertinent remarks, instrument approach, and runway
in use. The ceiling/sky condition, visibility, and
obstructions to vision may be omitted from the ATIS
broadcast if the ceiling is above 5,000 feet and the
visibility is more than 5 miles. The departure runway
will only be given if different from the landing
runway except at locations having a separate ATIS for
departure. The broadcast may include the appropriate
frequency and instructions for VFR arrivals to make
initial contact with approach control. Pilots of aircraft
arriving or departing the terminal area can receive the
continuous ATIS broadcast at times when cockpit
duties are least pressing and listen to as many repeats
as desired. ATIS broadcast shall be updated upon the
receipt of any official hourly and special weather. A
new recording will also be made when there is a
change in other pertinent data such as runway change,
instrument approach in use, etc.
SAMPLE BROADCAST-
DULLES INTERNATIONAL INFORMATION SIERRA.
1300ZULU WEATHER. MEASURED CEILING THREE
THOUSAND OVERCAST. VISIBILITY THREE, SMOKE.
TEMPERATURE SIX EIGHT. WIND THREE FIVE ZERO
AT EIGHT. ALTIMETER TWO NINER NINER TWO. ILS
RUNWAY ONE RIGHT APPROACH IN USE. LANDING
RUNWAY ONE RIGHT AND LEFT. DEPARTURE
RUNWAY THREE ZERO. ARMEL VORTAC OUT OF
SERVICE. ADVISE YOU HAVE SIERRA.
9.6.3_Pilots should listen to ATIS broadcasts
whenever ATIS is in operation.
9.6.4_Pilots should notify controllers on initial
contact that they have received the ATIS broadcast by
repeating the alphabetical code word appended to the
broadcast.
EXAMPLE-
_Information Sierra received."
9.6.5_When the pilot acknowledges receipt of the
ATIS broadcast, controllers may omit those items
contained on the broadcast if they are current.
Rapidly changing conditions will be issued by ATC
and the ATIS will contain words as follows:
EXAMPLE-
_Latest ceiling/visibility/altimeter/wind/(other conditions) will be issued by approach control/tower."
NOTE-
The absence of a sky condition/ceiling and/or visibility on
ATIS indicates a sky condition/ceiling of 5,000 feet or
above and visibility of 5 miles or more. A remark may be
made on the broadcast, _the weather is better than 5,000
and 5," or the existing weather may be broadcast.
9.6.6_Controllers will issue pertinent information to
pilots who do not acknowledge receipt of a broadcast
or who acknowledge receipt of a broadcast which is
not current.
9.6.7_To serve frequency-limited aircraft, FSSs are
equipped to transmit on the omnirange frequency at
most en route VORs used as ATIS voice outlets. Such
communication interrupts the ATIS broadcast. Pilots
of aircraft equipped to receive on other FSS
frequencies are encouraged to do so in order that these
override transmissions may be kept to an absolute
minimum. |
|