Go Back  PPRuNe Forums > Flight Deck Forums > Tech Log
Reload this Page >

Read and Do Checklist

Wikiposts
Search

Notices
Tech Log The very best in practical technical discussion on the web

Read and Do Checklist

Thread Tools
 
Search this Thread
 
Old 7th June 2007 | 08:19
  #1 (permalink)  
Thread Starter
 
Joined: Dec 2002
Posts: 43
Likes: 0
From: U.A.E
Read and Do Checklist

I am looking for a good definition of a "read and do" type checklist.
In my outfit there is some debate as to what this actually is.
Specifically the On Ground Emer/Evac Checklist on the A330/340.

Many in the training department say that a Read and do means that the
guy who reads it does all the required actions. I find this unwieldy.
As PIC am I supposed to sit there and watch while the FO Reads the checklist and then actions it? I think that if the FO reads the QRH and watches the Capt's actions and verifies them this is a much more effective use of two crew.

Any ideas or input?
Toubob is offline  
Reply
Old 7th June 2007 | 08:41
  #2 (permalink)  
 
Joined: Mar 2002
Aviation Qualifications: ATPL
Posts: 9,226
Likes: 995
From: Seat 1A
Good question. In flight, we action the abnormal checklist as a read and do, solely by the PNF, with the PF confirming switch selections before they are moved. This is to ensure the PF (or at least somebody) is still "flying the aeroplane" at all times.

On the ground we do the same, but there is a good argument (as you suggest) for the FO (we don't have PF/PNF on the ground, only Capt/FO) reading the drill and the Captain doing the actions with the FO confirming, the obvious difference being that the aeroplane isn't flying anymore and cannot get into strife with it's brakes parked!

However, you would then have two different procedures for inflight and OTG. It's probably been deemed better to have one procedure of both. If I had my way, the Captain would be doing the reading, as that is where the stuffups/omissions will be, not the moving of the actual switches. He is purportedly the most experienced crewmember and therefore the least likely to mess up reading the "do" list.
Capn Bloggs is offline  
Reply
Old 7th June 2007 | 10:24
  #3 (permalink)  
 
Joined: Jun 2002
Posts: 3
Likes: 5
From: Wor Yerm
Read and Do = Read the action required, do the action required and then check that the required action has been performed.

Challenge and response = Buttons are pressed and actions performed, the checklist is read and it is confirmed by the other guy(gal) that things are where they are meant to be.

Who presses is the buttons is another matter entirely although I think it depends on manufacturer, history and culture (and if you have a former fast jet pilot in the crew).

PM
Piltdown Man is offline  
Reply
Old 7th June 2007 | 10:26
  #4 (permalink)  
PPRuNe supporter
 
Joined: Dec 2003
Posts: 1,676
Likes: 0
From: Planet Earth
I agree

We have the same cock up on our EVAC procedures, first of all, I am the one that notifies TWR that we are evacuating, second of all I am the one that calls the cabin crew to stations and thirdly, I am the one that issues the actual evac commands.
Dream Land is offline  
Reply
Old 7th June 2007 | 22:35
  #5 (permalink)  
 
Joined: Jun 2002
Posts: 3
Likes: 5
From: Wor Yerm
There are also memory items. Ours are split into seat or function (PF/PNF) specific. They are simple and ours do work. For example, an evacuation is initiated from the left seat, the plane is shut down by the right and then "announced" by the left followed by a shut down. It is vital to do an evacuation slowly - it it too easy to chuck people into props/engines, have them clamber over wings with spoilers and/or flaps up etc. The last two evacuations I witnessed were cock-ups. In the first the aircraft was not configured and the second, amongst others, the order to evacuate was given on Box 1. We all heard, but the PAX didn't.

PM
Piltdown Man is offline  
Reply

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off



Contact Us - Archive - Advertising - Cookie Policy - Privacy Statement - Terms of Service

Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.