Briefing Guide for Order 7110

Briefing Guide - Basic

Table of Contents

Paragraph Number	Title
2-3-2	AREA/ROUTE BRIEFING PROCEDURES
2-3-3	MONITORING
2-4-3	CONTENT
6-1-2	FLIGHT PLANS
6-2-1	FLIGHT PLAN RECORDING
6-6-2	AMIS WITHIN AN ADIZ-DVFR
6-6-3	FORWARDING DVFR INFORMATION
6-6-5	ADDRESSING DVFR FLIGHT PLAN MESSAGES
7-2-3	INBOUND PRIVATE AIRCRAFT: ADIZ REQUIREMENTS

1. PARAGRAPH NUMBER AND TITLE: 2-3-2. AREA/ROUTE BRIEFING PROCEDURES AND 2-3-3. MONITORING

2. BACKGROUND: The ability to record messages and make them available to the pilot community via the telephone was a step forward in the provision of information to pilots, but building TIBS recordings has been a labor-intensive process for an AFSS specialist. The process often results in late recordings and variable quality due to human interpretive differences. Moreover, it results in the loss of a highly trained professional from his/her primary responsibility of pilot weather briefing. The further automation of repetitive tasks like TIBS is not only more cost-effective, but highly desirable from a standardization and quality assurance perspective. The automation of this process is contingent upon the ability to convert weather products from text to voice format, a process readily available with today's technology. Three basic types of TIBS recordings are made today, Area/Route briefings, Airspace Procedures and Special Announcements. Airspace Procedures and Special Announcements will continue to be manually produced. The purpose of TIBS is to provide a preview of weather conditions. However, accessibility is the biggest attraction for (or to) the pilot, compared to waiting on the telephone for a certified briefer.

3. CHANGE:

OLD		NEW
2-3-2. AREA/ROUTE BRIEFING PROCEDURES		2-3-2. AREA/ROUTE BRIEFING PROCEDURES
Title through a		No Change
Add		NOTE- For the purpose of TIBS broadcasts, an area briefing may be a geographic location not defined by a nautical mile radius, for example, NORTHWEST NEBRASKA.
PHRASEOLOGY- THIS RECORDING PREPARED AT (time) LOCAL or (time) ZULU. BRIEFING SUMMARY FOR: A (number of miles) NAUTICAL MILE RADIUS OF (location), or THE ROUTE FROM (location) TO (location).		PHRASEOLOGY- THIS RECORDING PREPARED AT (time) LOCAL or (time) ZULU. BRIEFING SUMMARY FOR: A (number of miles) NAUTICAL MILE RADIUS OF (location), or (location not defined by nautical mile radius), or THE ROUTE FROM (location) TO (location).
b. Adverse Conditions. Summarize WST, WS, WA, CWA, AWW, and any other available information that may adversely affect flight in the route/area.		b. Adverse Conditions. Include WST, WS, WA, CWA, AWW, UUA and any other available information that may adversely affect flight in the route/area.
*PHRASEOLOGY-*		No Change
c. VFR Not Recommended Statement. Include this recommendation when current or forecast conditions, surface or aloft, in your judgment would make flight under visual flight rules doubtful.		c. VFR Not Recommended Statement. Include this recommendation when current or forecast conditions, surface or aloft, would make flight under visual flight rules doubtful.
*PHRASEOLOGY-* through d		No Change
e. Current Conditions. Summarize the current weather conditions over the route/area. Include PIREPs on conditions reported aloft and radar reports or a summary of observed radar echoes from local equipment. Specific departure/destination observations may be included.		e. Current Conditions. Include current weather conditions over the route/area and PIREPs on conditions reported aloft.
*NOTE-* through f		No Change
g. En Route Forecast. Summarize from appropriate data; e.g., FAs, prognosis charts, weather advisories. Provide the information in a logical order; i.e., climb out, en route, and descent.		g. En Route Forecast. Include forecast information from appropriate data; e.g., FA Synopsis, TAFs and weather advisories.
h. Winds Aloft. Summarize winds aloft as forecast for the route/area as interpolated from forecast data for the local and/or the adjacent reporting locations for levels through 12,000 feet. The broadcast should include the levels from 3,000 to 12,000 feet, but shall always include at least two forecast levels above the surface.		h. Winds Aloft. Include winds aloft as forecast for the route/area as interpolated from forecast data for the local and/or the adjacent reporting locations for levels through 12,000 feet. The broadcast should include the levels from 3,000 to 12,000 feet, but shall always include at least two forecast levels above the surface.
i		No Change
PHRASEOLOGY- PILOT WEATHER REPORTS ARE REQUESTED. CONTACT FLIGHT WATCH OR A FLIGHT SERVICE STATION.		PHRASEOLOGY- PILOT WEATHER REPORTS ARE REQUESTED. CONTACT FLIGHT WATCH OR FLIGHT SERVICE, AS APPROPRIATE.
NOTE- Delete all reference to FLIGHT WATCH when not available at time of broadcast.		Delete
j through k		No Change
l		Delete
m		Renumber l

OLD		NEW
2-3-3. MONITORING		2-3-3. MONITORING
Meteorological recordings shall be monitored immediately after recording and as necessary to insure accuracy of data. Nonmeteorological recordings shall be monitored and checked for quality and accuracy immediately after recording and once each shift. After each recording, the TIBS shall be checked for availability by calling 1-800-WX-BRIEF or a locally designated phone number. Subsequent checks may be accomplished using local monitoring.		a. Manually prepared meteorological recordings shall be monitored immediately after recording and as necessary to insure accuracy of data. Non-meteorological recordings shall be monitored and checked for quality and accuracy immediately after recording and once each shift. After each recording, the TIBS shall be checked for availability by calling 1-800-WX-BRIEF or a locally designated phone number. Subsequent checks may be accomplished using local monitoring.
Add		b. Automated TIBS products shall be monitored once each shift to ensure clarity and accuracy.

1. PARAGRAPH NUMBER AND TITLE: 2-4-3. CONTENT

2. BACKGROUND: The purpose of the HIWAS service is to alert pilots to hazardous weather along their routes of flight. Automation of the HIWAS recordings and processes is a critical piece of Lockheed-Martin (LM) FS21 Flight Service Station concept, both operationally and financially. Recent National Weather Service (NWS) message formats and the improvement of text-to-voice software have made it possible to create HIWAS broadcasts with computers at central locations and disseminate them via remote communication outlets, nationwide. Lockheed Martin's automation of the HIWAS product will use an electronic map/database to locate and distribute weather advisories and state-of-the-art, text-to-voice software to convert NWS reports to voice for broadcast. The FS21 system will produce a site-specific, customized broadcast for each HIWAS outlet or group of outlets.

3. CHANGE:

OLD		NEW
2-4-3. CONTENT		2-4-3. CONTENT
Title through *NOTE-*		No Change
b. Summary of WSTs, WSs, WAs, UUAs, AWWs, CWAs, and any other weather such as isolated thunderstorms that are rapidly developing and increasing in intensity, or low ceilings and visibilities that are becoming widespread which are considered significant and are not included in a current hazardous weather advisory.		b. Statement of hazardous weather, including WSTs, WSs, WAs, UUAs, AWWs, and CWAs.
c through d		No Change
PHRASEOLOGY- CONTACT FLIGHT WATCH OR FLIGHT SERVICE FOR ADDITIONAL DETAILS.		PHRASEOLOGY- CONTACT FLIGHT WATCH OR FLIGHT SERVICE, AS APPROPRIATE, FOR ADDITIONAL DETAILS.
NOTE- Delete all reference to FLIGHT WATCH when not available at time of broadcast.		Delete

1. PARAGRAPH NUMBER AND TITLE:
6-1-2. FLIGHT PLANS,
6-2-1. FLIGHT PLAN RECORDING,
6-6-2. AMIS WITHIN AN ADIZ-DVFR,
6-6-3. FORWARDING DVFR INFORMATION,
6-6-5. ADDRESSING DVFR FLIGHT PLAN MESSAGES, and
7-2-3. INBOUND PRIVATE AIRCRAFT: ADIZ REQUIREMENTS

2. BACKGROUND: DVFR procedures, as contained in FAAH 7110.10 and FAAH 7610.4, were developed over 25 years ago. Those procedures required that DVFR flight plan information be sent to the tie-in ARTCC, who then forwarded the information to NORAD. The pilot had to activate his/her flight plan (for SAR purposes) with the AFSS and then contact the ARTCC to obtain his/her beacon code and activate the DVFR flight plan. The ARTCC would then forward the activation time to NORAD. When these procedures were developed, DVFR traffic was low volume, and the procedures, while very work intensive, were acceptable for this level of activity. With the rapid development of oil fields, off both coasts and in the Gulf of Mexico that began during the late 1980s, and the resultant huge increase in helicopter traffic in support of these operations, the procedures quickly proved inadequate for the task.

In the mid 1990s, the Southwest Region began testing a new system for handling DVFR traffic. Using a PC with a Service B drop, the AFSS accepted and transmitted DVFR flight plans directly to NORAD using a specially created address, ZAM. The AFSS assigned the beacon code when the pilot filed his/her flight plan. This new system and procedure alleviated the burden on the ARTCC and only required one radio contact by the pilot on departure.

3. CHANGE:

OLD		NEW
6-1-2. FLIGHT PLANS		6-1-2. FLIGHT PLANS
Title through j		No Change
Add		k. When a pilot files a DVFR flight plan, advise the pilot to activate with Flight Service. Also advise the pilot that a discrete beacon code will be assigned upon activation.
Add		NOTE- 1. A discrete beacon code may be assigned when the flight plan is filed, as necessary. If the pilot wants to file a DVFR flight plan that departs outside the facility's flight plan area, provide the applicable toll-free number for the departure FSS. 2. Discrete beacon codes are assigned to facilities in accordance with FAAO 7110.66, National Beacon Code Allocation Plan.

OLD		NEW
6-2-1. FLIGHT PLAN RECORDING		6-2-1. FLIGHT PLAN RECORDING
Record flight plans on FAA Form 7233-1, on M1FC Domestic Flight Plan Mask, or on OASIS 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, 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:
*NOTE-* through a2		No Change
(a) V - civilian VFR flight plans.		(a) V - civilian VFR flight plans including DVFR.
(b) through (c)		No Change
(d) DV - DVFR flight plans. M1FC will accept DV flight plans only as a proposal addressed to an ARTCC.		(d) DV - Do not use. See para 6-6-3a.
(e) through 3		No Change
(a) VFR		(a) VFR - civilian VFR flight plans, including DVFR.
(b)		No Change
(c) DVFR		(c) DVFR - Do not use. See para 6-6-3a.
(d) through (i)		No Change
(j) DVFR STOPOVER		(j) DVFR STOPOVER - Do not use.

OLD		NEW
6-6-2. AMIS WITHIN AN ADIZ-DVFR		6-6-2. AMIS WITHIN AN ADIZ-DVFR
For security control of air traffic, specific information contained inflight plans filed by a pilot operating or proposing to operate in accordance with DVFR within an ADIZ shall be forwarded to the appropriate ARTCC.		For security control of air traffic, specific information contained in flight plans filed by a pilot operating or proposing to operate in accordance with DVFR within an ADIZ shall be forwarded to NORAD.
*NOTE-* Other offices, military and civil, which have direct communications with the appropriate ARTCC are permitted to forward DVFR flight plan data directly to the ARTCC. When pilots require normal handling of VFR flight plans, these offices are permitted to file a VFR flight plan with the AFSS/FSS and a DVFR flight plan with the ARTCC.		*NOTE-* Other offices, military and civil, as well as pilots, may file DVFR flight plans with an AFSS/FSS for forwarding to NORAD.

OLD		NEW
6-6-3. FORWARDING DVFR INFORMATION		6-6-3. FORWARDING DVFR INFORMATION
Forward DVFR flight plan information to the appropriate ARTCC by Service F interphone or Service B as follows:		Except for Alaska, forward DVFR flight plan information to NORAD via the Service B NORAD address or by telephone as follows:
Add		NOTE- 1. The following NORAD addresses are group addresses that include all appropriate NORAD sectors and law enforcement: KZAMZQZX - the contiguous 48 states and San Juan. PHIRAOCZ - Hawaii. 2. NORAD will not send an acknowledgement and must be manually acknowledged from the suspense list by the specialist. (NORAD Headquarters assumes responsibility for receipt.)
a. DVFR.		a. VFR.
Add		1. M1FC - DVFR flight plans shall be entered into the M1FC Flight Plan mask with "V" in the FR: field for processing purposes. The applicable NORAD address must be manually entered into the CP: field. If "NORIV," delete AFSS closure point address.
Add		2. OASIS - DVFR flight plans shall be entered into the OASIS Flight Plan dialog box with "VFR" selected in the Flight Rules (FR) drop-down list box for processing purposes. The applicable NORAD address must be manually entered into the Closure Points text box. If "NORIV," delete AFSS closure point address.
b through f		No Change
1. When the flight plan information is provided before the aircraft's departure, forward the proposed departure time.		1. When the flight plan information is provided before the aircraft's departure, enter as a proposal. Depart the flight plan immediately upon receipt of the actual departure time.
2		Delete
3. If arrangements cannot be made to obtain the actual departure time, forward the ETD.		2. If arrangements cannot be made to obtain the actual departure time, forward the estimated time of departure (ETD).
g		No Change
h. Route of flight.		h. ETA.
i		No Change
j. Remarks as appropriate.		j. Remarks.
1 through 5		Delete
Add		1. DVFR discrete transponder code.
Add		2. True airspeed.
Add		3. Estimated point of penetration of the ADIZ (latitude/longitude or fix-radial-distance).
Add		4. Estimated time of penetration of the ADIZ.
Add		5. If no arrival report (NORIV) will be filed with an appropriate aeronautical facility, include the abbreviation NORIV. Do not pass "NORIV" to NORAD. For Service B transmissions, precede "NORIV" remark with the percent (%) symbol.
Add		EXAMPLE- 1210 135 3442/9345 1446
Add		NOTE- On a proposed flight plan, a single "X" may replace the DVFR discrete transponder code, true airspeed, estimated point of penetration of ADIZ, or the estimated time of penetration.
Add		EXAMPLE- Missing true airspeed: 1210 X 3442/9345 1446 Missing estimated point of ADIZ penetration and time with NORIV: 1210 135 XX %NORIV

OLD		NEW
6-6-5. ADDRESSING DVFR FLIGHT PLAN MESSAGES		6-6-5. ADDRESSING DVFR FLIGHT PLAN MESSAGES
Forward DVFR flight plan information to the ARTCC in whose flight advisory area penetration of an ADIZ is intended unless special arrangements provide otherwise. (Reference para 6-6-3.)		Forward DVFR flight plan information (Reference para 6-6-3) as follows:
a. Contiguous U.S. ADIZ. (See TBL 6-6-1.)		a. Contiguous U.S. ADIZ. Forward DVFR flight plan information to NORAD.
TBL 6-6-1		Delete
b. Alaskan ADIZ. (See TBL 6-6-2.)		b. Alaskan ADIZ. Alaska ADIZ procedures are contained in a Letter of Agreement with the affected facility.
TBL 6-6-2		Delete
c. Hawaiian ADIZ.		c. Hawaiian ADIZ. Forward all DVFR flight plan information to NORAD.
*NOTE-* Forward all DVFR flight plan messages concerning flight in the Hawaiian ADIZ to the Honolulu ARTCC.		Delete
Add		1. M1FC - Enter "V" in the FR: field of the Flight Plan mask.
Add		2. OASIS - Select "VFR" in the Flight Rules drop-down list of the Flight Plan dialog box.
d. Canada. Routing DVFR flight plan messages.		d. Canada. Routing DVFR Flight Plan messages to Canada. Compose DVFR messages pertaining to aircraft operating on a DVFR flight into Canada using the same procedure as for DVFR messages in the contiguous 48 states, except add "DVFR" in remarks. In addition, address and route to the appropriate transborder tie-in station.
*NOTE-* Compose DVFR messages pertaining to aircraft operating on a DVFR flight into Canada in the same format as for DVFR messages in the U.S., address and route via Service B.		Delete

OLD		NEW
7-2-3. INBOUND PRIVATE AIRCRAFT: ADIZ REQUIREMENTS		7-2-3. INBOUND PRIVATE AIRCRAFT: ADIZ REQUIREMENTS
Title through c		No Change
d. Forward information on DVFR aircraft inbound to the U.S. to the appropriate ARTCC facility via NADIN or interphone. Forward actual departure times by interphone. Forward the following information:		d. Forward information on DVFR aircraft inbound to the U.S. to NORAD via Service B or by telephone. Forward the following information:
1. Aircraft call sign.		No Change
2. Number of aircraft.		2. Number and type of aircraft.
3. Type of aircraft.		Delete
4. Altitude.		3. Altitude (within ADIZ).
5 through 7		Renumber 4 through 6
8. Route of flight.		7. Destination.
9. Destination.		8. ETA.
10. Remarks. Estimated time and point of penetration of ADIZ, position reports, revisions to position reports for penetration point, other information deemed necessary for the security control of air traffic.		9. Remarks: DVFR discrete transponder code; estimated point of penetration of ADIZ (latitude/longitude or fix-radial-distance); estimated time of penetration of ADIZ.
Add		NOTE- 1. See para 6-6-3 for M1FC and OASIS transmission information.
*NOTE-* Further information on ADIZ requirements is contained in 14 CFR Part 99.		2. Further information on ADIZ requirements is contained in 14 CFR Part 99.