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

What Does "Challenge and Response" Mean

Thread Tools
 
Search this Thread
 
Old 9th Jun 2008, 08:33
  #21 (permalink)  
 
Join Date: Oct 2004
Location: Body
Posts: 130
Likes: 0
Received 0 Likes on 0 Posts
Simple:

Challenge and response =

PNF "Altimeters"

PF "Passing FL 120, descending 60, 1013 set"

PNF "Check"

Read and Do = PNF read and do...!
blueplume is offline  
Old 9th Jun 2008, 14:35
  #22 (permalink)  
 
Join Date: Sep 2005
Location: No one's home...
Posts: 416
Likes: 0
Received 0 Likes on 0 Posts
A37575 said
If the aircraft is already under control from start of take off run and climb away then any complacent relaxed delay in taking action to extinguish an engine fire warning is nothing less than sheer recklessness.
I think you misunderstand. The first rule is always to FLY THE AIRPLANE. There are myriad examples where the crew jumped on the problem and not only did not solve it in their rush, the compounded the problem.

I am not familiar with any incident or accident where a fire warning resulted in the wing burning off but I am familiar with a number of incidents where crews jumped on the wrong problem.

So, just to clarify positions.. do you or your company require you to immediately begin shutting down an engine the moment the fire light illuminates on takeoff? Do you climb to obstacle clearance altitude or a standard altitude and clean up (flaps up etc) before beginning the checklist? Do you have memory actions or have you/has your company changed to checklist items for eng fire/failure?

FWIW, at many US carriers, if you begin the fire checklist before cleaning up, it may result in a checkride failure and require retraining.

A few years ago, there was a report with the title PSM/ICR which stood for Propulsion System Malfunction/Improper Crew Response and it detailed how crews got themselves in trouble even with simple PSMs.

I, nor anyone else, is suggesting complacency is acceptable but you seem to advocate immediate action over a timely response. I do not agree and I doubt you can find events (crashes due to burned through hyd/fuel/etc) which support your position.

I could be wrong and stand ready to learn...
wileydog3 is offline  
Old 1st Jun 2011, 01:49
  #23 (permalink)  
 
Join Date: Nov 2004
Location: Aberdeen
Posts: 179
Likes: 0
Received 1 Like on 1 Post
In a previous job (4-eng turboprop), each pilot had an “after start scan/flow” done from memory, (mostly Left seat pilot actions, a few done by necessity from the RH seat, but importantly, rigidly specified as to who’s duty each item was). This was followed by an “After–start check” done as challenge and response. RP read the check aloud, LP made the responses for items he had actioned in the flow, RP responded to his own “challenge” if it was an item he had set. I found this a very good system. However…….

Seemed to work well, until the day we were distracted by external interruption during the checks, and somehow, despite calling “ Flaps – set and indicating”, they in fact were at zero. Fortunately, we survived the subsequent stick shaker after take-off and got airborne OK (yes – MOR was submitted). We are both sure that we did not miss the item in the challenge and response, but that we read the challenge and called the response without either of us checking it had been done.

After that, I modified my “response” slightly, and think that it has helped me to make sure that what I say is what is actually there.
Where the checklist might just say “Start select…………………OFF/Light out” , I would now respond to RP’s call of “Start select”, with “………. IS OFF/ Light IS out” . As I say the word “IS” it prompts me to make sure that I am actually checking the item as I say the words, and not just saying what should be set. A minor change, but it works for me……… (so far !!)

With reference to fire after take-off, on our aircraft (as I understand is fairly SOP in fixed-wing) the initial action was to fly the aircraft and do nothing about the fire until above a certain height (500’ in our case) (the only action below 500 was to feather a failed engine that had not autofeathered).
However, in both types of large helicopter I have operated, the standard briefing is “no engine to be shut down below 500’ except in case of fire” in which case the procedure is to immediately start the fire drill. Considering that the Lee-on-Solent S61 went from engine fire warning to starting to lose all hydraulic control as the pipes burned through just as they put it on the ground, all in less than 90 seconds, and subsequently burned to the ground, I think there are arguments for both ways of doing things…………
farsouth is offline  
Old 1st Jun 2011, 03:42
  #24 (permalink)  
 
Join Date: Jan 2011
Location: Where it's Too Cold
Posts: 113
Likes: 0
Received 0 Likes on 0 Posts
You only need one guy to read a checklist and touch/verify what he's doing..

Challenge and response is really at it's core, about making sure something is getting done, brought to someone's attention and the item/thing is solved/acted upon, etc....by two people.

'Fl180, Altimeter check'
'Set to 30.12'
And both people watch it being set the correct setting.

That's the kind of redundancy that should happen in a crew cockpit...if one guy just reads the check list, never really looks up, or checks that the other is actually doing the item and correctly...you might as well be a single pilot op, it's just busy work.
theficklefinger is offline  
Old 2nd Jun 2011, 12:48
  #25 (permalink)  
 
Join Date: Apr 2005
Location: Australia
Posts: 1,414
Likes: 0
Received 0 Likes on 0 Posts
During a recent 737 simulator recurrency session, the F/O was asked to conduct the whole start up procedure from dark cockpit to engines running all by himself without another crew member to prompt or help in any way. Without the use of a checklist he was completely out of his depth. It proved that he used checklists as a crutch for his lack of knowledge. He already had over 500 hours on type.. Areas of responsibility are fine until you are asked to know what is the other fellows area of responsibility as well.
A37575 is offline  
Old 10th Jun 2011, 11:03
  #26 (permalink)  
 
Join Date: Jun 2010
Location: Brisbane, Australia
Posts: 304
Likes: 0
Received 0 Likes on 0 Posts
In response to an earlier (much earlier!) comment regarding normal checklist responses, it was suggested that some c/l responses are "as required", meaning the specific response was variable, depending on the situation.

That's fine, though I haven't seen one in a checklist for quite some time.....my response to that response is that you never actually responded with "as required", you ALWAYS responded with the specific setting that was relevant at that time.

i.e. Engine Anti-Ice.....As required //was always responded to with On or Off!

In the back section of the QRH (for Boeings) there is a section that clearly lays out the only acceptable way to run any of the checklists within, be they Normal or Non-Normal.
EW73 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 © 2024 MH Sub I, LLC dba Internet Brands. All rights reserved. Use of this site indicates your consent to the Terms of Use.