曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

TBL 4-2-5
Flight Plan Closure
Command Result
CL ACID Flight plan closed.
CL ACID,
(remarks)
Flight plan closed with remarks.
c. M1FC IFR Flight Plans. The following commands
are normally used in the performance of IFR
flight plan functions.
1. Flight Plan Filing. (See TBL 4-2-6.)
TBL 4-2-6
Flight Plan Filing
Command Result
FP Displays blank domestic flight plan
mask.
(Fill in mask) Enter flight plan elements as
required.
GI Transmits flight plan with route
validation.
GI RO Transmits flight plan by-passing
route validation.
2/14/08 JO 7110.10T
Data Recording 4-2-3
2. Flight Plan Modification. (See TBL 4-2-7.)
TBL 4-2-7
Flight Plan Modification
Command Result
FP ACID Displays flight plan by ACID.
(Modify data) Modify flight plan elements as
required using TAB key.
STPM Existing flight plan replaced by
modified flight plan on proposed
list.
3. Cancel Flight Plan. (See TBL 4-2-8.)
NOTEOASIS
IFR Flight Plan. Use the flight plan functions to
record IFR flight plan filing, modification and
cancellation data. Detailed instructions are contained in
the WINGS online help and the WINGS System Users
Guide.
TBL 4-2-8
Cancel Flight Plan
Command Result
FP ACID Displays flight plan by ACID.
CX Flight plan cancelled.
CX (remarks) Flight plan cancelled with remarks.
4-2-4. PILOT WEATHER REPORTS
a. PIREPs are formatted for input into M1FC by
the use of “Display PIREP entry format (WY)”
keyword. The following commands are required to
transmit PIREPs via the PIREP mask. (See
TBL 4-2-9.)
TBL 4-2-9
PIREP Entry
Command Result
WY Displays the PIREP entry format
mask.
Formulate PIREP using either the free form area of
the mask, or the mask, but not both.
GI(s) (1) Transmits to the AWPs.
(2) Generates P alert flag at all
terminals enabled for P alerts within
FSDPS family.
b. In an AISR facility, use FAA Form 7110-2 or
material deemed appropriate.
c. PIREPs are formatted for input into OASIS by
using a Transmit PIREP dialog box. A properly
formatted pilot report will generate an Auto Update
alarm at designated workstations.
4-2-5. LOGGING AIRCRAFT CONTACTS
a. M1FC. Aircraft contacts and inflight briefings
are logged and stored on the DD file for
accountability. The required elements are:
1. Inflight Briefing (IB).
2. Type of Flight (TOF).
3. Type of Service (TOS).
4. ACID.
5. Remarks.
EXAMPLEIB
(TOF),(TOS),(ACID), REMARKS.
NOTEIf
current partial exists, ACID is optional.
(See TBL 4-2-10.)
TBL 4-2-10
Type of Flight
TOF (TYPE OF FLIGHT)
IC IFR AIR CARRIER
IG IFR GENERAL
IM IFR MILITARY
IT IFR AIR TAXI
VC VFR AIR CARRIER
VG VFR GENERAL
VM VFR MILITARY
VT VFR AIR TAXI
Example: “IGI” = IFR General ICAO.
For DVFR, replace “V” with “D.”
For ICAO, add “I” to TOF.
TOS (TYPE OF SERVICE)
A ACFT contact & airport advisory
AB ACFT contact, airport advisory &
briefing
B ACFT contact & briefing
BLANK ACFT contact
(See TBL 4-2-11.)
JO 7110.10T 2/14/08
4-2-4 Data Recording
TBL 4-2-11
Contacts & Inflight Briefings
CB This is used to log
general information
in the DD file
without adding to
the traffic count.
Current partial is
by-passed.
IB DG,,N1234, “Remarks” ACFT contact,
DVFR General,
ACID in current
partial by-passed.
IB IG,,,ALSTG ACFT contact, IFR
General, Remarks.
IB IGI,B,N1,VNR ACFT contact, IFR
General ICAO,
Briefing, ACID in
current partial
by-passed,
Remarks.
IB VM,B,, “Remarks” ACFT contact,
VFR Military,
Briefing.
IB VG,A,, “Remarks” ACFT contact,
VFR General,
Airport Advisory.
IB ,,N1,Remarks This is used to log
additional radio
contacts.
b. OASIS. Aircraft contacts and inflight briefings
are logged and stored in the history files for
accountability.
NOTEACID
and Flight Rules are required to log an inflight
briefing or aircraft contact.
c. In the REMARKS block, locally approved
contractions and identifiers may be used for
frequently used terms not listed in either FAAO
JO7340.2, Contractions or FAAO JO 7350.8,
Location Identifiers.
d. If the inflight position is recorded, you may
limit entries in the REMARKS to those necessary for
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：FSS飛行服務站1(28)