|
Table of Contents
|
Paragraph
Number |
Title |
|
1-3-2 |
DUTY PRIORITY |
|
3-2-1 |
CONDUCT OF STANDARD BRIEFING |
|
4-1-1 |
INFLIGHT SERVICES |
|
4-4-1 |
GENERAL |
|
6-1-5 |
TELEPHONE REQUESTS FOR ATC CLEARANCES |
|
6-2-1 |
FLIGHT PLAN RECORDING |
|
13-1-1 |
PURPOSE |
|
13-1-2 |
DUTIES |
|
13-1-3 |
MALFUNCTIONS |
|
13-1-4 |
AIRCRAFT REPORTED MALFUNCTIONS |
|
13-1-5 |
ADJUSTMENT TO NAVAIDS |
|
13-1-6 |
NAVAID FLIGHT CHECK |
|
13-1-7 |
MONITORING OF NAVAIDS BY TECHNICAL
OPERATIONS SERVICES PERSONNEL |
1. PARAGRAPH
NUMBER AND TITLE: 1-3-2. DUTY PRIORITY and 4-1-1. INFLIGHT SERVICES
2. BACKGROUND: In 2005 when flight
services outside of Alaska were contracted to a private vendor, the monitoring
of NAVAIDS was classified as a realigned activity, therefore it is a function no
longer provided by flight service stations (FSSs). FSSs in Alaska do not monitor
NAVAIDS.
3. CHANGE:
|
OLD |
|
NEW |
|
1-3-2. DUTY PRIORITY |
|
1-3-2. DUTY PRIORITY |
|
Title through a3 |
|
No Change |
|
b. Emergency situations are those
where life or property is in immediate danger. Inflight 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
NAVAID monitoring and restoration, LAA, delivery of ATC clearances,
advisories or requests, issuance of military flight advisory messages, EFAS,
NOTAM, SAR communications searches, flight plan handling, transcribed or
live broadcasts, weather observations, PIREPs, and pilot briefings.
Preflight services are those which directly affect aircraft operations but
which are provided prior to actual departure and usually by telephone. These
include pilot briefings, recorded data, flight plan filing/processing, and
aircraft operational reservations |
|
b. Emergency situations are those
where life or property is in immediate danger. Inflight 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
airport advisories, delivery of ATC clearances,advisories or
requests, issuance of military flight advisory messages, EFAS, NOTAM, SAR
communications searches, flight plan handling, transcribed or live
broadcasts, weather observations, PIREPs, and pilot briefings. Preflight
services are those which directly affect aircraft operations but which are
provided prior to actual departure and usually by telephone. These include
pilot briefings, recorded data, flight plan filing/processing, and aircraft
operational reservations. |
|
OLD |
|
NEW |
|
4-1-1. INFLIGHT SERVICES |
|
4-1-1.
inflight services
|
|
Inflight services are those provided to
or affecting aircraft inflight or otherwise operating on the airport
surface. This includes services to airborne aircraft, such as NAVAID
monitoring and restoration, LAA, delivery of ATC clearances, advisories
or requests, issuance of military flight advisory messages, EFAS, NOTAM, SAR
communications searches, flight plan handling, transcribed or live
broadcast, weather observations, PIREPs, and pilot briefings. |
|
Inflight services are those provided to
or affecting aircraft inflight or otherwise operating on the airport
surface. This includes services to airborne aircraft, such as airport
advisories, delivery of ATC clearances, advisories or
requests, issuance of military flight advisory messages, EFAS, NOTAM, SAR
communications searches, flight plan handling, transcribed or live
broadcast, weather observations, PIREPs, and pilot briefings. |
1. PARAGRAPH NUMBER AND TITLE: 3-2-1
CONDUCT OF A STANDARD BRIEFING
2. BACKGROUND: In 2002, providing
information on the Special Flight Rules Area in Washington, DC and the
associated Prohibited Areas during a pilot weather briefing changed from an upon
request item to a mandatory briefing item. When the requirement became mandatory
the old upon request guidance remained in place, creating confusion with respect
to both mandatory and upon request items. Furthermore, to emphasize the
importance of NOTAMs concerning the Prohibited Areas and the Special Flight
Rules Area, sub-paragraph b8(a) is divided into b8(a) and b8(b). The remaining
changes are: 1) deleting references to specific operating systems, such as Model
1 Full Capacity (M1FC) which is obselete, and OASIS, which has its own system
user's guide; 2) deleting references to local NOTAMs, which were discontinued in
January 2008; 3) deleting references to non-automated Alaska facilities since
all facilities now operate with OASIS; 4) reorganizing sub-paragraphs b8 and b12
for continuity and to remove redundant references to the Prohibited Areas in
b12(a) Note 1; 5) remove the 100 NM restriction to pilot-requested special use
airspace information in para b12(a); 6) the word “incomplete” is changed to
“updated periodically” in b12(a) because the SUA NOTAM databases are now
essentially complete, but still subject to last minute changes; and 7) SUA
NOTAMs issued under SUAE, SUAC and SUAW accountability locations are generally
considered “upon request” briefing items, with the exception of Restricted Area,
Aerial Refueling and Night Vision Goggle NOTAMs, because briefing tools used by
FAA and others cannot tag these types of NOTAMs to a specific route of flight.
3. CHANGE:
|
OLD |
|
NEW |
|
3-2-1 CONDUCT OF A STANDARD BRIEFING
|
|
3-2-1 CONDUCT OF A STANDARD BRIEFING
|
|
Title through b7 |
|
No Change |
|
8. Notices to Airmen (NOTAM).
|
|
8. Notices to Airmen (NOTAM).
Provide NOTAM information pertinent to the flight:
|
|
(a) Provide available NOTAM
(L) (Flight Plan Area), NOTAM (D), and Prohibited Areas P-40, P-49,
P-56, and the Special Flight Rules Area for Washington, DC, information
pertinent to the flight. |
|
(a) NOTAM (D). All NOTAMs
(D), including Special Use Airspace (SUA) NOTAMs for
Restricted Areas, Aerial Refueling, and Night Vision Goggles (NVG).
|
|
Add |
|
NOTE-
Other SUA NOTAMs (D), such as Military Operations Area (MOA), Military
Training Route (MTR) andWarning Area NOTAMs, are considered “upon request”
briefing items as indicated in paragraph 3-2-1b12(a). |
|
Add |
|
(b) Prohibited Areas P-40, P-49,
P-56 and the Special Flight Rules Area (SFRA) for Washington, DC.
|
|
(b) For M1FC and OASIS
facilities, provide Flight Data Center (FDC) NOTAM which are
pertinent to the proposed flight and are not already carried in the
Notices to Airmen publication. |
|
(c) Flight Data Center (FDC)
NOTAMs not already carried in the Notices to Airmen
publication. |
|
NOTE-
OASIS separates Temporary Flight Restriction (TFR) NOTAM
from other FDC and General FDC NOTAM in the Weather and Aeronautical
Briefing Window under a separate tabbed page labeled TFR. |
|
Delete |
|
(c) For nonautomated
Alaska FSS facilities, provide FDC NOTAM within 400 NM radius of your
facility which are pertinent to the proposed flight and are not already
carried in the Notices to Airmen publication. |
|
Delete |
|
NOTE-
If approved by the Flight Services Operations Area Office, the area may
be adjusted to meet user requirements. |
|
Delete |
|
b8(d) through b11 |
|
No Change |
|
12. Upon Request |
|
12. Upon Request.
Provide any information requested by the pilot, including, but not limited
to: |
|
(a) In addition to pertinent D
NOTAM, provide information available to your position of operation on
Special Use Airspace (SUA), SUA related airspace (i.e., Air Traffic Control
Assigned Airspace (ATCAA)) and military training route (MTR) activity
within your flight plan area plus an additional 100 NM extension. For
all SUA and MTR data requests, advise the pilot that information may be
incomplete and to contact the appropriate ATC facility for additional
information while in flight. |
|
(a) Special Use Airspace,
except those listed in paragraph 3-2-1b8(a), SUA related
airspace (i.e., Air Traffic Control Assigned Airspace (ATCAA)) and military
training route (MTR) activity. For all SUA and MTR data requests, advise the
pilot that information may be updated periodically and to
contact the appropriate ATC facility for additional information while in
flight. |
|
NOTE-
1. Pertinent D NOTAM include: Restricted Areas,
Refueling Tracks, Prohibited Areas P-40, P-49, P-56, and the Special Flight
Rules Area for Washington, DC. |
|
Delete |
|
2. For air
to ground positions utilize information obtained from Special Use
Airspace/In-Flight Service Enhancement (SUA/ISE) and Model 1 Full
Capacity/Operational and Supportability Implementation System (M1FC/OASIS).
For all other positions utilize information obtained from M1FC/OASIS.
|
|
Delete |
|
3. SUA and
related airspace includes the following types of airspace: Alert Area,
Military Operations Area (MOA), Prohibited Area, Restricted Area,
Refueling Anchor, Warning Area and Air Traffic Control Assigned Airspace
(ATCAA). MTR data includes the following types of airspace: IFR Training
Routes (IR), VFR Training Routes (VR), Slow Training Routes (SR) and
Aerial Refueling Tracks (AR). |
|
NOTE-
For the purpose of this paragraph, SUA and related airspace
includes the following types of airspace: Alert Area, Military Operations
Area (MOA), Warning Area and Air Traffic Control Assigned Airspace (ATCAA).
MTR data includes the following types of airspace: IFR Training Routes (IR),
VFR Training Routes (VR),and Slow Training Routes (SR). |
|
(b) Review the
appropriate aeronautical publications and inform the pilot of pertinent
NOTAM, special notices, and other information about Prohibited Areas P-40,
P-49, P-56, and the Special Flight Rules Area for Washington, DC, when
pertinent to the flight. |
|
Delete |
|
(c) Provide approximate
density altitude data. |
|
(b) Approximate
density altitude data. |
|
|
|
|
|
(d) Provide information
regarding such items as air traffic service and rules, customs/immigration
procedures, ADIZ rules, SAR, Flight Watch, etc. |
|
(c) Information
regarding such items as air traffic service and rules, customs/immigration
procedures, ADIZ rules, SAR, Flight Watch, etc. |
|
(e) Provide LORAN C
NOTAM. |
|
(d) LORAN C NOTAMs.
|
|
REFERENCE-
FAAO 7930.2, Para 5-3-7c, NOTAM (D)
NAVAID. |
|
REFERENCE-
FAAO 7930.2, Para 5-3-7o,
NOTAM (D) NAVAID. |
|
(f) Provide military
NOTAM. |
|
(e) Military
NOTAMs. |
|
REFERENCE-
FAAO 7930.2, Para 8-3-1, Military NOTAM
Availability. |
|
REFERENCE-
FAAO 7930.2, Para 8-3-1, Military NOTAM
Availability |
|
(g) Provide GPS
Receiver Autonomous Integrity Monitoring (RAIM) Aeronautical Information.
RAIM information shall be provided 1-hour before to 1-hour after the ETA, or
a time frame requested by the pilot. |
|
(f) GPS Receiver
Autonomous Integrity Monitoring (RAIM) Aeronautical Information. RAIM
information shall be provided 1-hour before to 1-hour after the ETA, or a
time frame requested by the pilot. |
|
(h) Provide runway
friction measurement NOTAMs. |
|
(g) Runway
friction measurement NOTAMs. |
|
(i) Provide Special FDC
instrument approach procedure changes. |
|
(h) Special
FDC instrument approach
procedure changes. |
1. PARAGRAPH NUMBER AND TITLE: 4-4-1.
GENERAL
2. BACKGROUND: In Alaska, the
Automatic Flight Information Service (AFIS) is now available and procedures here
are added for guidance to flight service stations where AFIS and other Airport
Advisory Services are provided.
Paragraph 4-4-1.h.4 contains instructions for the specialist when a pilot
requests a special VFR clearance. This sub-paragraph pertains to the entire
section, so it is removed and placed in a separate paragraph.
3. CHANGE:
|
OLD |
|
NEW |
|
4-4-1 GENERAL |
|
4-4-1 GENERAL |
|
Title through h3 |
|
No Change |
|
4. If the pilot requests
special VFR clearance, provide the appropriate elements and follow the
procedures in Section 5. |
|
i. If the pilot requests
special VFR clearance, provide the appropriate elements and follow the
procedures in Chapter 4, Section 5, Special VFR
Operations. |
|
Add |
|
j. Automatic Flight Information
Service (AFIS) is available, confirm receipt of the current AFIS information
if the pilot does not initially state the appropriate AFIS code. Issue the
current AFIS information to pilots who are unable to receive the AFIS.
|
|
Add |
|
EXAMPLE-
“Verify you have information ALFA.” |
|
|
|
|
1. PARAGRAPH NUMBER AND TITLE: 6-1-5.
TELEPHONE REQUESTS FOR ATC CLEARANCES
2. BACKGROUND: Over the last several
years, there have been a number of situations where a flight service specialist
received a call from a pilot located outside the geographical area that the
specialist normally is responsible for due to increased use of cell phones
and/or flight service stations covering larger geographical areas of the
country. Many states have airports with city names that are the same as cities
in other states. Often airports within the same state have similar sounding
names. This situation has created a safety issue when a pilot calls for an ATC
clearance and the flight service specialist or ATC assumes the aircraft plans to
depart one airport when in fact it is another airport. If the flight plan was
initially entered into the system with the wrong departure point due to
miscommunication, or the flight plan was entered correctly but can't be found
due to misunderstanding of the location, clearances have been created to
accommodate the pilot assuming the flight plan was lost. The clearances were
passed to the pilot who accepted the clearance, none the wiser, and departed
from an airport different than the airport ATC was expecting. As a result of
these types of errors, the FAA Office of Safety Investigations issued Safety
Recommendation 05.372 to revise the Aeronautical Information Manual (AIM). In
response, the AIM was updated to highly recommend to pilots that they clearly
identify their departure airport. Since pilots are not bound by AIM
recommendations, this proposal amends FAA Order JO 7110.10 to require flight
service specialists to positively verify the departure location by airport name
or location identifier, and the city name and state.
3. CHANGE:
|
OLD |
|
NEW |
|
6-1-5.
telephone requests for atc
clearances |
|
6-1-5.
telephone requests for atc
clearances |
|
Add |
|
When a telephone request for an
ATC clearance is received, positively verify the departure location by
airport name or location identifier, and the city name and state.
|
|
Add |
|
NOTE-
1. With telephone calls being received from larger geographic areas,
verification of the departure location may prevent a critical safety
situation involving similar or identical airport or city names possibly
located in different states. |
|
Add |
|
2. City refers to a city,
town, village or publicly recognized place. |
|
Add |
|
3. Refer to FAAO JO 7110.10,
Para 4-3-7, ATC Clearances, Advisories, or Requests, for guidance on
relaying ATC clearances. |
1. PARAGRAPH NUMBER AND TITLE: 6-2-1.
flight plan recording
2. BACKGROUND: Five changes are
being made to this paragraph:
1) On June 29, 2008 all FAA ARTCC Host computer systems switched from Domestic
Flight Plan (FAA Form 7233-1) processing to International Flight Plan (FAA Form
7233-4) processing for those pilots wishing to receive automated assignment of
RNAV arrival and departure routes. This change adds a Note at the end of the
first paragragh explaining when an international flight plan form will be used
to file a flight plan in domestic U.S. airspace.
2) Tables 6-2-2 and 6-2-3 are added in conjunction with FAA Order JO 7110.65
para 2-3-5, Aircraft Identity. VC-25 flight management system (FMS) upgrades and
subsequent implementation of future air navigation (FANS) procedures has driven
the need to reevaluate the Air Force One (A1) and Air Force Two (A2) call signs.
To use these services, the aircraft must register and file a call sign with at
least three digits. Also, the call signs for the President's and Vice
President's family member's aircraft are changed to EXEC1F and EXEC2F,
respectively, regardless of branch of service. Previously, the call signs were
AF1F, VM1F, etc.
3) Olive Drab “OD” is added as an official contraction to FAA Form 7233-1, Item
16, Color of Aircraft.
4) This change also deletes all references to Model 1 Full Capacity,
which is no longer used; and OASIS, where operating instructions can be found in
the OASIS System Users Guide.
5) “Homebuilt” is changed to “amateur-built” at the request of the
Experimental Aircraft Association (EAA) per FAR 21.191(g).
3. CHANGE:
|
OLD |
|
NEW |
|
6-2-1.
flight plan recording
|
|
6-2-1.
flight plan recording
|
|
Record flight plans on FAA Form 7233-1,
M1FC Domestic Flight Plan Mask, or in the OASIS Domestic Flight Plan
dialog box. Completion of all blocks or fields is not required in every
case, and all items filed are not always transmitted. Use authorized
abbreviations where possible. Complete as follows: |
|
Record flight plans on FAA Form 7233-1,
or electronic equivalent. Completion of all blocks or fields
is not required in every case, and all items filed are not always
transmitted. Use authorized abbreviations where possible. The
instructions below are for completion of FAA Form 7233-1, Flight Plan. For
electronic versions of flight plan forms, refer to that system's operating
instructions. |
|
NOTE-
OASIS. For detailed instructions on the Domestic Flight Plan
dialog box, refer to the WINGS online help or the WINGS System Users Guide.
|
|
NOTE-
Use FAA Form 7233-4, International Flight Plan, for international
flights as well as flights in domestic U.S. airspace in which automatic
assignment of RNAV routes is desired. See paragraph 6-2-3, Flight Plans with
Area Navigation (RNAV) Routes in Domestic U.S. Airspace.
|
|
a. Item 1. Type of flight
plan. |
|
a. Item 1. Type of flight
plan. Check the appropriate box. |
|
a1 through a3(j) |
|
Delete |
|
b. Item 2. Aircraft
Identification (M1FC- AI: field. OASIS - Aircraft ID text box). Enter
as follows, but do not exceed seven alphanumeric characters: |
|
b. Item 2. Aircraft
Identification. Enter as follows, but do not exceed seven alphanumeric
characters: |
|
b1 |
|
No Change |
|
EXAMPLE |
|
No Change |
|
NOTE- |
|
No Change |
|
2. U.S. Military Aircraft. Use
the military abbreviation followed by the last five digits of the aircraft's
number. For certain tactical mission aircraft, enter the assigned
three-to-six letter code word followed by a one-to-four digit number. (See
TBL 6-2-1) |
|
2. U.S. Military Aircraft. |
|
|
|
(a) Use the military
abbreviation followed by the last five digits of the aircraft's number. For
certain tactical mission aircraft, enter the assigned three-to-six letter
code word followed by a one-to-four digit number. (See TBL 6-2-1)
|
|
TBL 6-2-1 |
|
No Change |
|
Add |
|
(b) Aircraft carrying the
President, Vice Presidential, and and/or their family members will use the
identifiers in the following tables. (See TBL 6-2-2 and TBL 6-2-3)
|
|
|
Add |
|
TBL 6-2-2
President and Family |
|
|
|
|
Service |
President |
Family |
|
|
|
|
Air Force |
AF1 |
EXEC1F |
|
|
|
|
Marine |
VM1 |
EXEC1F |
|
|
|
|
Navy |
VV1 |
EXEC1F |
|
|
|
|
Army |
RR1 |
EXEC1F |
|
|
|
|
Coast Guard |
C1 |
EXEC1F |
|
|
|
|
Guard |
G1 |
EXEC1F |
|
|
|
|
Commercial |
EXEC1 |
EXEC1F |
|
|
|
|
|
|
|
|
|
|
Add |
|
TBL 6-2-3
Vice President and Family |
|
|
|
|
Service |
Vice President |
Family |
|
|
|
|
Air Force |
AF2 |
EXEC2F |
|
|
|
|
Marine |
VM2 |
EXEC2F |
|
|
|
|
Navy |
VV2 |
EXEC2F |
|
|
|
|
Army |
RR2 |
EXEC2F |
|
|
|
|
Coast Guard |
C2 |
EXEC2F |
|
|
|
|
|
Guard |
G2 |
EXEC2F |
|
|
|
|
Commercial |
EXEC2 |
EXEC2F |
|
|
b3 |
|
No Change |
|
TBL 6-2-2 |
|
Renumber TBL 6-2-4
|
|
c. Item 3. Aircraft Type
(M1FC- AT: field. OASIS - Aircraft Type text box). Insert the name or
abbreviation (two-to-four alphanumeric characters) of the manufacturer's or
military designation. For homebuilt/experimental aircraft, use HXA,
HXB, or HXC in accordance with the FAAO JO 7340.2, Contractions. Spell out
aircraft type in Remarks. |
|
c. Item 3. Aircraft Type.
Insert the name or abbreviation (two-to-four alphanumeric characters) of the
manufacturer's or military designation. For amateur-built/experimental
aircraft, use HXA, HXB, or HXC in accordance with the FAAO JO 7340.2,
Contractions. Spell out aircraft type in Remarks. |
|
NOTE-
OASIS. OASIS validates all aircraft types in accordance
with FAAO JO 7340.2, Contractions. Nonstandard contractions will be
rejected. |
|
Delete |
|
c1 through c2 |
|
No Change |
|
TBL 6-2-3 |
|
Renumber TBL 6-2-5
|
|
NOTE-
The /E and /F suffixes will only be used by aircraft operating to
and from airports within the U.S., unless authorized by the controlling
authority. |
|
No Change |
|
REFERENCE-
FAAO JO 7110.65, Para 2-3-7 and TBL 2-3-7, Aircraft Equipment
Suffix. |
|
REFERENCE-
FAAO JO 7110.65, Para 2-3-8
and TBL 2-3-10, Aircraft Equipment Suffixes.
|
|
d. Item 4. True Airspeed
(TAS Knots) (M1FC- TS: field. OASIS - Airspeed text box). Enter
two-to-four digits for TAS in knots; M followed by three digits for Mach
number; or SC for “speed classified.” |
|
d. Item 4. True Airspeed
(TAS Knots) Enter two-to- four digits for TAS in knots; M followed by three
digits for Mach number; or SC for “speed classified.” |
|
e. Item 5. Departure
Point. |
|
e. Item 5. Departure
Point. Enter two-to-twelve alphanumeric and slant characters for name
or identifier of the departure airport or point over which the flight plan
is activated. |
|
1. M1FC- DD: field. Enter
two-to-twelve alphanumeric and slant characters for name or identifier of
the departure airport or point over which the flight plan is activated.
|
|
Delete |
|
NOTE-
Names may be used when there is no identifier available
and they do not exceed 12 characters with no spaces. Unless a geographic
point is converted to latitude/longitude or fix-radial-distance (FRD), the
M1FC computer will not be able to provide weather/NOTAM information and the
route override function must be used to transmit or modify the flight plan.
|
|
Delete |
|
2. OASIS - Departure
text box. Enter the departure point as follows: 2-5 alphanumeric character
LOCID, 8-11 character fix-radial-distance or 9-12 character
latitude/longitude. |
|
Delete |
|
f. Item 6. Departure Time.
|
|
f. Item 6. Departure Time.
Enter departure time in UTC. |
|
1. M1FC- TM: field.
Enter departure time in UTC. Prefix this time with a P in the TM:
field for proposals or a D for departures. If the departure time is assumed,
indicate this in the Remarks field. |
|
Delete |
|
2. OASIS - ETD text
box. Enter the proposed or actual time of departure as follows: {(DD)HHMM :
DD = 01-31, HH = 00-23, MM = 00-59}. |
|
Delete |
|
NOTE-
OASIS does not use prefixes (i.e., “P” or “D”) to
determine a proposed or actual time of departure. This determination is made
based on which button is used for filing. |
|
Delete |
|
g. Item 7. Cruising
Altitude (M1FC- AE: field. OASIS - Enroute Altitude text box).
Proposed altitude or flight level using two-to-seven characters; e.g., 80 or
080, OTP, OTP/125, VFR, ABV/060. |
|
g. Item 7. Cruising
Altitude. Proposed altitude or flight level using two-to-seven characters;
e.g., 80 or 080, OTP, OTP/125, VFR, ABV/060. |
|
h. Item 8. Route of Flight
(M1FC- RT: field. OASIS - Route text box.). Enter identifiers for
airways or jet routes to clearly indicate the proposed flight path. For
direct flight, use names or identifiers of navigation aids, Navigation
Reference System (NRS) waypoints, and geographical points or coordinates. If
more than one airway or jet route is to be flown, clearly indicate the
transition points. |
|
h. Item 8. Route of
Flight. Enter identifiers for airways or jet routes to clearly indicate the
proposed flight path. For direct flight, use names or identifiers of
navigation aids, Navigation Reference System (NRS) waypoints, and
geographical points or coordinates. If more than one airway or jet route is
to be flown, clearly indicate the transition points. |
|
NOTE-
1. On some direct flights beyond the departure center's airspace, it
may be necessary to include a fix in the adjacent center's airspace or
latitude/longitude coordinates, as appropriate, to facilitate computer
acceptance. Local procedures should be applied to these special situations.
|
|
No Change |
|
2. NRS waypoints
consist of five alphanumeric characters, which include the ICAO Flight
Information Region (FIR) identifier, followed by the letter corresponding to
the FIR subset (ARTCC area for the contiguous U.S.), the latitude increment
in single digit or group form, and the longitude increment. |
|
No Change |
|
EXAMPLE-
“KD34U” |
|
No Change |
|
i. Item 9. Destination.
|
|
i. Item 9. Destination.
Enter two-to-twelve alphanumeric and/or slant characters for name or
identifier of the destination airport or point over which the flight plan is
to be cancelled. |
|
1. M1FC- AD: field.
Enter two-to-twelve alphanumeric and/or slant characters for name or
identifier of the destination airport or point over which the flight plan is
to be cancelled. |
|
Delete |
|
2. OASIS - Destination
text box. Enter the destination airport or point over which the flight plan
is to be cancelled as follows: 2-5 alphanumeric character LOCID, 8-11
character fix-radial-distance or 9-12 character latitude/longitude. |
|
Delete |
|
j. Item 10. Estimated Time
Enroute (M1FC- TE: field. OASIS - Time Enroute text box). Enter in
hours and minutes the total elapsed time between departure and destination;
e.g., 0430 or 4+30. For IFR proposals, ETE must be in four-digit format;
i.e., 0215. |
|
j. Item 10. Estimated Time
Enroute. Enter in hours and minutes the total elapsed time between departure
and destination in four-digit format, i.e., 0215. |
|
NOTE-
OASIS facilities, enter the four digit enroute time in
hours and minutes; hhmm: hh=00-99, mm=00-59. |
|
Delete |
|
k. Item 11. Remarks (M1FC-
RM: field. OASIS - Remarks text box). Information necessary for ATC or to
assist search and rescue operations, plus any other data appropriate to the
flight; e.g., the abbreviations FAA or DOT. Enter names of experimental or
homebuilt aircraft (Veri-EZ, Long-EZ, Mustang, Delta Dart). For RM: field
only - Use 1-80 characters beginning with *, #, $, or %. (See TBL 6-2-4.)
|
|
k. Item 11. Remarks.
Information necessary for ATC or to assist search and rescue operations,
plus any other data appropriate to the flight; e.g., the abbreviations FAA
or DOT. Enter names of experimental or amateur-built aircraft
(Veri-EZ, Long-EZ, Mustang, Delta Dart). For RM: field only – Use 1-80
characters beginning with *, #, $, or %. (See TBL 6-2-6.) |
|
TBL 6-2-4 |
|
TBL 6-2-6 |
|
NOTE-
1. OASIS automatically inserts the appropriate symbol
according to the flight plan type (i.e., $-VFR, * -IFR)1. 2. Civil
aircraft with authorized company identification are required to file the
full authorized radio call in remarks. |
|
Delete |
|
1. Item 12. Fuel on Board
(M1FC- FB: field. OASIS - Fuel Capacity text box). Enter in hours and
minutes; e.g., 0330 or 3+30. |
|
l. Item 12. Fuel on Board. Enter
in hours and minutes in four-digit format; e.g., 0330. |
|
NOTE-
OASIS facilities, enter the fuel capacity; hhmm: hh=00-99,
mm=00-59. |
|
Delete |
|
m. Item 13. Alternate Airport/s.
|
|
m. Item 13. Alternate Airport/s.
Enter the location identifier if specified by the pilot. |
|
1. (M1FC- AA: field).
Enter the location identifier if specified by the pilot. For AA: field only.
Use three-to-seven alphanumeric characters. For two alternate airports,
enter identifiers consecutively; e.g., BJCFNL. |
|
Delete |
|
2. OASIS - Alternate
Airport text box. Enter the location identifier of a single alternate
airport in 3-4 alphanumeric characters. Additional alternate airports may be
entered in the Remarks text box as nontransmitted information. |
|
Delete |
|
n. Item 14. Pilot's Name,
Telephone Number, Aircraft's Home Base (M1FC- PD: field. OASIS - Pilot
Data text box). Self-explanatory. For military pilots, obtain the name
and telephone of BASOPS. |
|
n. Item 14. Pilot's Name,
Telephone Number, Aircraft's Home Base. Self-explanatory. For military
pilots, obtain the name and telephone of BASOPS. |
|
NOTE-
Pilot's name not required if BASOPS' name is provided. |
|
No Change |
|
o. Item 15. Number Aboard
(M1FC- NB: field. OASIS - Number On Board text box).
Self-explanatory. |
|
o. Item 15. Number Aboard.
Self-explanatory. |
|
p. Item 16. Color
of Aircraft. (M1FC- CR: field. OASIS - Aircraft Color text box). Use
authorized contractions when available. (See TBL 6-2-5.) |
|
p. Item 16. Color of
Aircraft. Use authorized contractions when available. (See TBL 6-2-7.)
|
|
TBL 6-2-5
Code and Color |
|
TBL 6-2-7
Code and Color |
|
Code |
Color |
|
Code |
Color |
|
Code |
Color |
|
Code |
Color |
|
A |
Amber |
|
B |
Blue |
|
A |
Amber |
|
B |
Blue |
|
BE |
Beige |
|
BK |
Black |
|
BE |
Beige |
|
BK |
Black |
|
BR |
Brown |
|
G |
Green |
|
BR |
Brown |
|
G |
Green |
|
GD |
Gold |
|
GY |
Gray |
|
GD |
Gold |
|
GY |
Gray |
|
M |
Maroon |
|
O |
Orange |
|
M |
Maroon |
|
O |
Orange |
|
P |
Purple |
|
PK |
Pink |
|
OD |
Olive Drab |
|
P |
Purple |
|
R |
Red |
|
S |
Silver |
|
PK |
Pink |
|
R |
Red |
|
T |
Tan |
|
TQ |
Turquoise |
|
S |
Silver |
|
T |
Tan |
|
V |
Violet |
|
W |
White |
|
TQ |
Turquoise |
|
V |
Violet |
|
Y |
Yellow |
|
|
|
|
W |
White |
|
Y |
Yellow |
1.
PARAGRAPH NUMBER AND TITLE: 13-1-1. purpose, 13-1-2. duties, 13-1-3.
malfunctions, 13-1-4. aircraft reported malfunctions, 13-1-5. adjustment to
navaids, 13-1-6. navaid flight check, and 13-1-7. monitoring of navaids by
technical operations services personnel,
2. BACKGROUND: In 2005 when flight
services outside of Alaska were contracted to a private vendor, the monitoring
of NAVAIDS was classified as a realigned activity, therefore it is a function no
longer provided by flight service stations (FSSs). FSSs in Alaska do not monitor
NAVAIDS.
3. CHANGE:
|
Chapter 13. NAVAID MONITORING
|
|
Delete |
|
Section 1. GENERAL |
|
Delete |
|
13-1-1. PURPOSE
|
|
Delete |
|
13-1-3. MALFUNCTIONS
|
|
Delete |
|
13-1-4. AIRCRAFT
REPORTED
MALFUNCTIONS |
|
4-1-6. AIRCRAFT
REPORTED NAVAID
MALFUNCTIONS |
|
a1 |
|
No Change |
|
2. If the second aircraft reports
normal operations, continue use and, if able, inform the first
aircraft. Record the incident on FAA Form 7230-4. |
|
2. If the second aircraft reports
normal operations, if able, inform the first aircraft. Record the incident
on FAA Form 7230-4. |
|
3. If the second aircraft
confirms the malfunction or, in the absence of a second aircraft report,
take NAVAID restoral action. |
|
3. If the second aircraft
confirms the malfunction: |
|
Add |
|
(a) Notify the appropriate IFR
control facility or sector. |
|
Add |
|
(b) Notify Technical Operations
personnel. |
|
Add |
|
(c) Take NOTAM action, if
necessary. |
|
Add |
|
(d) Record the incident on FAA
Form 7230-4. |
|
Add |
|
4. In the absence of a second
aircraft report: |
|
Add |
|
(a) Notify Technical Operations
and advise what time the initial aircraft reported the failure and when a
second aircraft report might be obtained. |
|
Add |
|
(b) Record the incident on FAA
Form 7230-4. |
|
4. If normal operation
is reported after restoral action is taken, continue use, record the
incident on FAA Form 7230-4, and notify appropriate maintenance personnel.
|
|
Delete |
|
5. If continued
malfunction is reported after restoral action is taken, request advice from
maintenance personnel on whether the NAVAID should be shut down. In the
absence of a second aircraft report, advise maintenance personnel of the
time of the initial aircraft report and the estimated time a second aircraft
report could be obtained. |
|
Delete |
|
b1 through b2 |
|
No Change |
|
3. Forward this information to
the local Traffic Management Unit (TMU) and local Maintenance
Control Center (MCC) personnel. |
|
3. Forward this information to
the Traffic Management Unit (TMU) and Technical Operations
personnel. |
|
c1 through c2 |
|
No Change |
|
3. If the pilot reports loss of
all WAAS service, report as a GPS anomaly using procedures in paragraph
13-1-4b. |
|
3. If the pilot reports loss of
all WAAS service, report as a GPS anomaly using procedures in paragraph
4-1-6b. |
|
13-1-5. ADJUSTMENTS
TO NAVAIDs |
|
Delete |
|
13-1-6. NAVAID
FLIGHT CHECK |
|
4-1-7. NAVAID
FLIGHT CHECK |
|
13-1-7. MONITORING
OF NAVAIDs BY
TECHNICAL OPERATIONS SERVICES
PERSONNEL. |
|
Delete |
|
