PPRuNe Forums - View Single Post - How do you brief the approach plate?
View Single Post
Old 6th Jul 2008, 08:22
  #19 (permalink)  
frontlefthamster
 
Join Date: Dec 2007
Location: France
Posts: 481
Likes: 0
Received 0 Likes on 0 Posts
The brief needs to be finished well before you anticipate receiving your first descent clearance. This is how I like to do it and see it done:

First, the big picture: aircraft status, notams, weather, a quick word about anything specific (eg low QNH day = level bust risk, new purser in charge so seat belts on early, plan to start manual flight early, or whatever else is notable about today's flight).

Then the arrival, from the plate, including terrain matters, and especially, clearance limits.

Then the approach, from the plate, including terrain matters. I like the Briefing Strip (TM).

Then the landing and taxi in, including flap and autobrake setting (referenced from the Perf Inflight), planned use of reverse, etc.

Then the missed approach, in full, intentions (and this might include a brief on the approach at an alternate if it's close by), fuel remaining, etc. There's no point having an SOP call of 'tune radio aids for missed approach' if your colleague dooesn't know what to set and where, before he hears it.

Then the opportunity for questions, and discussion of any points not already resolved.

Yes, interactive is a great method, provided your company supports it (and there's no excuse not to) and that you've been trained how to do it properly and in particular to do it effectively and non-confrontationally. For example, 'What do you believe is the Cat 1 minimum?' not 'What is the Cat 1 minimum?'. Focus the interactive elements on the important stuff.

But, most importantly I believe, the brief must be a story: it must be sequential, and told as a narrative of events. It should state what is going to be done, and when, and by whom. It should be listenable and engaging. It should inquire. It should seek out doubt and confusion and run them hard to ground. It must expand outside itself, into checking the nav aid set up and FMS, etc, and it must retract into itself to give unambiguous clarity, as for example, if revising standard calls for an autoland. It should be given, with enthusiasm and care, and listened and responded to attentively.

Two final points: the brief should be as long as it needs to be, and should cover everything of relevance without wasting time; briefing is too often done poorly. There is no excuse for this.
frontlefthamster is offline