37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1323555 |
Time | |
Date | 201601 |
Aircraft 1 | |
Make Model Name | B737 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Plan | IFR |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy |
Narrative:
Many of the new fos I fly with are under the mistaken impression that they must brief the engine inoperative go-around procedure on every leg where there is an engine failure on takeoff procedure (t-procedure). They tell me they were taught this in 737 school at the training center.this is incorrect. The flight operations manual (fom) is very clear; 'prior to an actual engine inoperative approach or when required by 10-7 page instructions; review obstacles and terrain in the missed approach path and brief the appropriate go-around procedure'; in other words; unless you are doing an actual engine inoperative approach; there is no need to brief the engine inoperative go-around.in fact; one could argue that it's not even safe to do so. The fom is very clear that we are only allowed to brief one approach at a time. Similarly; we should only be briefing one go-around at a time. Briefing two different go-around procedures for one approach will likely result in neither one of them being done correctly.I'm told that it used to be a [merger partner] requirement to brief the engine inoperative go-around procedure even when flying an all-engine approach. I don't know if this is true; but maybe it explains why the 737 instructors are still teaching this incorrectly. Regardless of the reason; they need to stop. We do not brief the engine inoperative go-around unless we're flying an actual engine inoperative approach.if this used to be a [merger partner] requirement; there are probably a lot of other pilots doing this incorrectly as well; which could be confusing to new fos. Perhaps a pilot bulletin highlighting the fom language and correct procedure is in order.
Original NASA ASRS Text
Title: B737 Captain reported that new First Officers the he flies with are under the mistaken impression that they must brief the engine inoperative go-around procedure for every approach to an airport with a special engine out missed approach procedure.
Narrative: Many of the new FOs I fly with are under the mistaken impression that they must brief the engine inoperative go-around procedure on every leg where there is an engine failure on takeoff procedure (T-procedure). They tell me they were taught this in 737 school at the training center.This is incorrect. The Flight Operations Manual (FOM) is very clear; 'Prior to an actual engine inoperative approach or when required by 10-7 page instructions; review obstacles and terrain in the missed approach path and brief the appropriate go-around procedure'; In other words; unless you are doing an actual engine inoperative approach; there is no need to brief the engine inoperative go-around.In fact; one could argue that it's not even safe to do so. The FOM is very clear that we are only allowed to brief one approach at a time. Similarly; we should only be briefing one go-around at a time. Briefing two different go-around procedures for one approach will likely result in neither one of them being done correctly.I'm told that it used to be a [merger partner] requirement to brief the engine inoperative go-around procedure even when flying an all-engine approach. I don't know if this is true; but maybe it explains why the 737 instructors are still teaching this incorrectly. Regardless of the reason; they need to stop. We do not brief the engine inoperative go-around unless we're flying an actual engine inoperative approach.If this used to be a [merger partner] requirement; there are probably a lot of other pilots doing this incorrectly as well; which could be confusing to new FOs. Perhaps a pilot bulletin highlighting the FOM language and correct procedure is in order.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.