Wikiposts
Search

Notices
Safety, CRM, QA & Emergency Response Planning A wide ranging forum for issues facing Aviation Professionals and Academics

Who does what

Thread Tools
 
Search this Thread
 
Old 3rd March 2005 | 06:42
  #1 (permalink)  
Thread Starter
 
Joined: Jun 2000
Posts: 17
Likes: 0
Who does what

I would appreciate some info on who does what during abnormal/emergencies on B737. At my company at the moment we have a lively discussion on the matter and outside info should be valuable in finalising our SOP.
I.e: during engine fire after take-off who is shuting down an engine, PF, PNF, Capt.
and shoulld Capt take-over even if F/O (PF) is dooing a good job.

I beleive this is a perfect case where CRM principles should be used in designing procedure, but I would love to hear from other people.
gaga1976 is offline  
Old 3rd March 2005 | 07:33
  #2 (permalink)  
 
Joined: Oct 2002
Posts: 345
Likes: 0
From: The dark side of the moon
At my airline it calls for the Captain the take control of the aircraft in emergency, however it is up to captain to choose when this is appropriate.

We drill for the PF to intiate engine shut down.
E.g. Fire bell after V1:

P.F: (at or above 600ft) Call for 'Engine Fire/Separtion recall items'
and then proceeds to close throttles; Disconnect AT; Start Lever to Idle Cut-off... All actions confirmed by PNF. After this is completed PF calls for continuation of recall items, which is carried out by the PNF.

Sorry got to run, will add more later!
Touch'n'oops is offline  
Old 3rd March 2005 | 19:06
  #3 (permalink)  
 
Joined: Aug 2001
Posts: 755
Likes: 0
From: Europe-the sunshine side
On our comp:
The f/o will remain PF if it was PF before the emergency.
The cpt will not assign f/o as PF if a emergency is on course and cpt is PF.
In case of eng fire:
After V1-cancel fire bell (PNF)
Above 400' ,a/c under controll,gear up -PF calls for the recall items on eng fire/sev damage & separation ,and after checking with the PNF the correct engine selected ,disengage a/t &reduce thrust then dictate the rest of the recalls and PNF executes-start levers,fire switch....
Check the QRH ,CI for recomendations regarding use of checklists.
Brgds Alex
alexban is offline  
Old 4th March 2005 | 02:40
  #4 (permalink)  
 
Joined: Oct 2002
Posts: 345
Likes: 0
From: The dark side of the moon
I believe the Captain should take control once the emergency has been delt with and the aircraft is returning for landing.

If the captain takes control too early his/her decision making will be slower and less thought will be given to his/hers actions. Manually flying the aircraft requires the concentration that could be better spent on making good decisions!

Let the F/O fly (as long as he is handling it well) and the Captain carry out check-lists and radio work. Because the Captain has the final say, it would be easier if he/she gave intentions directly to the controller not through a worked up F/O.

chink... chink!!!... There's my two cents worth!!!!
Touch'n'oops is offline  
Old 4th March 2005 | 13:17
  #5 (permalink)  
20 Anniversary
 
Joined: Jun 2003
Posts: 19
Likes: 0
From: Europe
Our company:

PF responsibilities:

flight path & airspeed control
a/c configuration
navigation

PNF:

monitoring
checklists
actions requested by PF

Both pilots may carry out memory items.

If COP is PF, duties must be changed after clean up. In all cases CDR shall perform approach and landing.
Dualcouple is offline  
Old 4th March 2005 | 16:32
  #6 (permalink)  
 
Joined: Feb 2000
Posts: 108
Likes: 0
From: UK
What if the weather dictates the use of a monitored approach?
earnest is offline  

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.