37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1397882 |
Time | |
Date | 201610 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B737 Next Generation Undifferentiated |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Component | |
Aircraft Component | GPWS |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Aircraft Equipment Problem Less Severe Flight Deck / Cabin / Aircraft Event Other / Unknown |
Narrative:
We were approaching the runway 10L hold short line on a line up and wait clearance with an RNAV departure clearance. As we got close to the line; we heard a tower transmission that began with 'our airline...' but; of course; we couldn't clearly hear what was said because the runway awareness and advisory system (raas) was blasting in our ears with its completely pointless announcement that we were approaching a runway. We were fairly sure we'd heard 'cleared for takeoff' somewhere in there but; just to be sure; we asked for a repeat. Sure enough; we'd been cleared for takeoff; but there has also a turn to a heading clearance that we absolutely had not heard.had we not asked for a repeat; had we assumed that we'd been cleared for takeoff even though we couldn't clearly hear the communication due to the raas; we would have launched and departed in LNAV; and violated our revised clearance that we'd been unable to hear.the raas caused this event; as it has so many times before.in my experience; never even once has the so called safety system provided any benefit whatsoever. It has; however; time and time again; provided outstanding annoyance and lost communication incidents during a critical phase of flight.get rid of it before it causes an accident.
Original NASA ASRS Text
Title: A B737NG Captain reported the EGPWS Runway Awareness and Advisory System (RAAS) alert interfered with what the crew assumed was their takeoff clearance. To be certain; the crew asked ATC to repeat; which is when the crew realized if they had accepted the assumed clearance a departure heading would have been missed.
Narrative: We were approaching the Runway 10L hold short line on a line up and wait clearance with an RNAV departure clearance. As we got close to the line; we heard a Tower transmission that began with 'Our airline...' but; of course; we couldn't clearly hear what was said because the Runway Awareness and Advisory System (RAAS) was blasting in our ears with its completely pointless announcement that we were approaching a runway. We were fairly sure we'd heard 'cleared for takeoff' somewhere in there but; just to be sure; we asked for a repeat. Sure enough; we'd been cleared for takeoff; but there has also a turn to a heading clearance that we absolutely had not heard.Had we not asked for a repeat; had we assumed that we'd been cleared for takeoff even though we couldn't clearly hear the communication due to the RAAS; we would have launched and departed in LNAV; and violated our revised clearance that we'd been unable to hear.The RAAS caused this event; as it has so many times before.In my experience; never even once has the so called safety system provided any benefit whatsoever. It has; however; time and time again; provided outstanding annoyance and lost communication incidents during a critical phase of flight.Get rid of it before it causes an accident.
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.