PPRuNe Forums - View Single Post - Calling Malfunctions on Takeoff
View Single Post
Old 11th Apr 2004, 07:07
  #1 (permalink)  
FlareArmed
 
Join Date: Jun 2003
Location: Australia
Posts: 128
Likes: 0
Received 0 Likes on 0 Posts
Calling Malfunctions on Takeoff

I am interested in gathering some information on what various operators policy is on calling malfunctions on takeoff, particularly for non-EICAS installations such as my current type, the B737NG.

For some background, the QRH has the following to say about abnormalities on the takeoff:

Rejected Takeoff

The decision to reject a takeoff rests solely with the Captain. The Captain must make the decision so stopping action can begin by V1. If the decision is to reject the takeoff, the Captain should clearly announce "Reject", commence the stopping action, and assume control of the airplane. If the First Officer is making the takeoff, the First Officer should not abandon control of the airplane until the Captain makes a positive input on the controls.

Prior to 80 knots, the takeoff should be rejected for system failures(s), unusual noise or vibration, tire failure, abnormally slow acceleration, engine failure, engine fire, unsafe takeoff configuration warning, predictive windshear, or if the airplane is unsafe to fly.

Above 80 kts, reject for engine failure, fire, predictive windshear warning, or if the airplane is unsafe or unable to fly

During the takeoff, the crew member recognizing the malfunction will call it clearly and precisely


Some questions:

1. How exactly do you call a system failure below 80 kts?

2. Do you call all malfunctions above 80 kts, or just the problems to reject for (some aircraft inhibit non-abort system failures above 80 kts)?

3. When a failure does occur, are key words used or is it left up to the individual?

4. Do any operators allow for the First Officer to make the reject decision?
FlareArmed is offline