Build a briefing that answers real flight questions

Begin with the flight you actually intend to make

A useful briefing starts with a defined question: can this pilot, aircraft and route work at the intended time, with workable alternatives? The FAA AC 91-92: Pilot’s Guide to a Preflight Briefing presents self-briefing as a process of planning, interpretation and risk assessment. Collecting screenshots without evaluating them is not the same task.

Write the departure window, route, likely arrival time, aircraft limitations and personal concerns on one page. If your timing or route changes, mark which parts of the briefing need another look.

Work through four decision areas

• Weather: What could make departure, the route or arrival unsuitable? What is uncertain, and when would you need a new observation or forecast?
• Airports: Are the intended runway, services and arrival options usable for this flight?
• Airspace and navigation: What restrictions, outages or changes could alter the route?
• Alternatives: What would make you delay, divert or cancel rather than continue?

The FAA AIM: Preflight explains that automated resources can support a compliant briefing and that Flight Service can help with interpretation. Brief yourself first, then bring specific unresolved questions rather than asking someone to interpret an unfamiliar route from scratch.

Use a change log, not just a download date

Try a short personal note with these columns: item reviewed, issue found, decision made, and recheck needed. For example: “Arrival timing uncertain — review destination forecast again before departure.” This is an organizational aid, not a required form or a replacement for your normal planning process.

Keep the last check separate

Before departure, revisit what changed since the first review. A briefing made earlier can still be useful context, but it does not freeze conditions in place. Save the source references and note questions that still need an answer.

Common misunderstanding: a downloaded route or a green readiness indicator in an app does not mean the pilot has completed a weather and NOTAM briefing. FLAL’s offline preparation and the pilot’s operational assessment are different jobs.