Section 2. Pilot Briefing

1. DESCRIPTION

Pilot briefings are the gathering, translation, interpretation, and summarization of weather and aeronautical information into a form usable by the pilot or flight supervisory personnel to assist in flight planning and decision-making for the safe and efficient operation of aircraft. These briefings may include, but are not limited to, weather observations, forecasts and aeronautical information (for example, NOTAMs, military activities, flow control information, and TFRs).

1. PILOT WEATHER BRIEFER CERTIFICATION

Flight service specialists must be certified to provide pilot briefings. Pilot weather briefer certification criteria is defined in FAA Order JO 7220.4, FAA Certification of Pilot Weather Briefer. The order details procedures and responsibilities for the FAA Pilot Weather Briefer Certification Program.

1. LOGGING BRIEFINGS

1. Briefings must be logged and retained in accordance with FAA Order 1350.14, Records Management. Briefings must be logged in operational systems when possible but may be logged manually, if needed.
2. Operational systems must, at a minimum, automatically record the facility/sector/vendor, date, position, time, and, for specialist‐provided services, the specialist identification for each logged briefing. In addition, enter the following information:

1. Departure and destination.
2. Aircraft identification. The pilot's name may be substituted for the aircraft identification, if unknown.
3. Remarks, as applicable, to indicate type of briefing, and/or VNR.

1. To manually log pilot briefings, use one of the following FAA forms:

1. FAA Form 7233-2, Preflight Briefing Log. Use a separate form each day. Two or more forms may be used simultaneously at different operating positions. Complete boxes 1 through 3 on each form. Enter appropriate data in columns 4, 5, 6, 7, 8 (if pertinent), and 9. If the pilot's name is known, it may be substituted for the aircraft identification. As applicable, enter OTLK (outlook briefing), AB (abbreviated briefing), and/or VNR in column 8.
2. FAA Forms 7233-5, In‐flight Contact Record, or 7230-21, Flight Progress Strip - FSS. Enter PB in block 14 if a briefing is provided. As applicable, also enter AB, OTLK, and/or VNR in the same block.

1. Where audio recorders are used, facility management may limit entries on pilot briefing records to those required for facility use.
2. Where fast-file recorders are used and the pilot states the source of a briefing on the recorder, the source must be entered in the remarks field of the flight plan.

1. TYPE OF BRIEFING TO BE DELIVERED

1. There are three basic briefing packages:

1. Standard. A comprehensive briefing within six hours of departure.
2. Abbreviated. To update specific information as soon as practicable.
3. Outlook. For early planning; six hours or more before flight.

1. Provide the pilot with the type of briefing requested (standard, abbreviated, or outlook).

1. When it is not clear which type briefing is desired, provide the items requested and then determine if the pilot would like a standard briefing.
2. If a standard briefing is requested, conduct the briefing in accordance with paragraph 5-2-5.
3. If the pilot does not request a standard briefing, provide either an abbreviated briefing in accordance with paragraph 5-2-6 or an outlook briefing in accordance with paragraph 5-2-7.

1. DELIVERY OF STANDARD BRIEFINGS

Standard briefings provide a complete and detailed depiction of the weather elements and aeronautical information for the intended flight. A standard briefing may be obtained within six hours of estimated time of departure (ETD) and may be requested multiple times for flights during dynamic weather.

1. Background information. Obtain the following information if not evident or already known:

1. Type of flight planned (VFR or IFR).
2. Aircraft identification or pilot's name; for pre‐stored profiles, confirm aircraft identification and pilot's name.
3. Aircraft type.
4. Departure point.
5. Route of flight.
6. Destination.
7. Flight altitude(s).
8. ETD and estimated time en route (ETE).

1. International cautionary advisory. Issue the following advisory for briefings with international departures, arrivals, or routes of flight. This advisory may be omitted if the pilot advises it has been received or the system indicates the pilot has opted out of receiving the statement.

1. Using all available sources of weather and aeronautical information, provide the following data as applicable to the proposed flight. Provide the information in subparagraphs c1 through c11 in the sequence listed, if known, except as noted.

1. Adverse conditions.

1. Include this element when meteorological or aeronautical conditions are reported or forecast that may influence the pilot to alter the proposed flight.
2. Emphasize conditions that are particularly significant, such as:

1. Low‐level wind shear.
2. Density altitude.
3. Thunderstorms.
4. Icing.
5. Frontal zones along the route of flight.
6. Adverse NOTAMs (for example, airport/runway closures, air traffic delays, TFRs, or special flight rules areas [SFRA]).

1. Weather advisories must include the type of advisory (for example, G-AIRMET, SIGMET, or CWA) followed by the pertinent information, regardless of delivery method (for example, specialist-provided or automated).
2. Include urgent PIREPs (UUA) when appropriate.

1. VFR Flight Not Recommended (VNR).

1. Specialists must include this statement when VFR flight is proposed and sky conditions or visibilities are reported or forecast, surface or aloft, that, in your judgment, would make flight under VFR doubtful.

1. This element should not be provided as a blanket statement when the reported conditions, forecast, and/or trends, do not support it.
2. This element may be provided at the beginning of the briefing or combined with the applicable adverse conditions for emphasis.
3. A description of the conditions, affected locations, and times must be included to provide justification, clarity, and mutual understanding.
4. Automated systems may include this statement when the system identifies one or more conditions that would make flight under VFR uncertain.

1. Check Density Altitude.

1. Include this statement when flight is proposed to depart from and/or land at an airport with field elevations of 2,000 feet MSL or higher and temperatures, present or forecast, meet the criteria contained in TBL 5-2-1.
2. Upon request, provide approximate density altitude data.

1. Synopsis.

1. Provide a brief statement describing the type, location, and movement of weather systems and/or air masses that might affect the proposed flight.
2. Automated systems may deliver the information using graphics.
3. This element may be combined with adverse conditions and/or the VNR element, in any order, when it will help describe the conditions.

1. Current conditions.

1. Summarize from all available sources reported weather conditions applicable to the flight including but not limited to: departure airport reports (for example, aviation routine weather reports [METAR], weather camera analysis, etc.), PIREPs, clouds, visibilities, and precipitation.
2. Emphasize information that confirms or refutes weather advisories.
3. This element may be omitted, with pilot's concurrence, if the proposed time of departure is beyond two hours, or if requested by the pilot.
4. Automated systems may deliver the information using a variety of methods (for example, graphics, text, or dynamic displays).

1. Forecast.

1. Summarize from all available sources forecast information applicable to the proposed route and altitude(s) including but not limited to departure airport forecast and area forecast (graphical or textual based on the location), if in the briefer's judgment, it provides a better picture, clouds, visibilities, icing, turbulence, and precipitation.
2. Provide the forecast wind in knots and degrees referenced to true north, and provide temperatures in degrees Fahrenheit. Interpolate wind directions and speeds between levels and stations as necessary.

1. Provide the destination forecast, including significant changes expected within one hour before and after the ETA.
2. Provide trends that confirm or refute weather advisories.
3. Provide the information in a logical order: departure, climb out, en route, descent, and arrival.

1. NOTAMs.

1. Provide pertinent NOTAMs for the departure, en route, and destination including those for special activity airspace (SAA) such as restricted areas, aerial refueling tracks and anchors, and lights out/night vision goggle operations.

1. Combine this element with adverse conditions when it might influence the pilot to alter the proposed flight (for example, airport/runway closures, air traffic delays, and TFRs).

1. Prohibited areas P-40, P-56, and the SFRA for Washington, DC. Include this element when pertinent to the route of flight. Advise the pilot that VFR flight within 60 miles of the DCA VOR/DME requires special awareness training, unless the pilot advises they are aware of the requirement or the system indicates the pilot has opted out of receiving the advisory.

1. ATC delays. Inform the pilot of ATC delays and/or flow control advisories that might affect the proposed flight.
2. PIREP" id="SOLICIT_PIREP">Solicitation of PIREPs. Request a report when in your judgment, a report of actual in‐flight conditions is beneficial or when conditions meet criteria for solicitation of PIREPs (see Chapter 8, Section 1).

1. This element should not be provided as a generic statement.
2. To the extent possible, the solicitation should be accompanied by a specific request.

1. Advise pilots they may contact an FSS to report en route conditions.

1. Upon Request. Provide any information requested by the pilot, if available (for example, approximate density altitude data, customs/immigration procedures, ADIZ rules, other published information, FDC NOTAMs, and military NOTAMs).

1. DELIVERY OF ABBREVIATED BRIEFINGS

Abbreviated briefings emphasize the more dynamic briefing elements that may have changed since a standard briefing was obtained. It helps the users focus on specific risk areas for the intended flight in an efficient manner and allows users to be proactive in reacting to changing conditions while in‐flight.

1. Obtain background information in accordance with subparagraph 5-2-5a.
2. If applicable, issue the international cautionary advisory in accordance with subparagraph 5-2-5b.
3. When a pilot desires specific information, only provide the requested information. If adverse conditions are reported or forecast, advise the pilot. At the pilot's request, provide details on these conditions, in accordance with subparagraphs 5-2-5c1-c3.
4. When a pilot requests an update to a previous briefing, obtain from the pilot the time the briefing was received if not evident or already known. To the extent possible, limit the briefing to appreciable changes in meteorological and aeronautical conditions since the previous briefing. Provide the information in the sequence listed in paragraph 5-2-5.
5. When a pilot requests to file a flight plan only, and adverse conditions are reported of forecast for the proposed route, ask if the pilot requires the information. If requested, provide details on these conditions, in accordance with subparagraph 5-2-5c1-c3).
6. Solicit PIREPs in accordance with subparagraph 5-2-5c10.

1. DELIVERY OF OUTLOOK BRIEFINGS

Outlook briefings provide a general indication of which elements may be a factor during a flight and should only be used during planning six hours or more from the ETD.

1. Conduct the briefing in accordance with paragraph 5-2-5. Omit items in subparagraphs c2, c3, c5, and c6(b) through c10, unless specifically requested by the pilot or deemed pertinent by the specialist.
2. When the proposed flight is scheduled to be conducted beyond the valid time of the available forecast data, provide a general outlook and then advise the pilot when complete forecast data will be available for the proposed flight.