 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An air carrier pilot discusses the loud and unnecessary raas warning as the crew lines up on the departing runway to hold for crossing traffic.
| Attributes | |
| ACN | 809544 |
| Time | |
| Date | 200810 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : sea.airport |
| State Reference | WA |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | ground : position and hold |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Experience | flight time last 90 days : 180 flight time type : 8000 |
| ASRS Report | 809544 |
| Events | |
| Anomaly | aircraft equipment problem : less severe |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : unable |
| Supplementary | |
| Problem Areas | Aircraft Company |
| Primary Problem | Company |
Narrative:
We were cleared position and hold on runway 16 left at sea. As we aligned with the runway the raas system announced 'on runway 16 left' at the same time that tower issued instructions to an air carrier Y flight exiting runway 16 center down field. We had a much greater need to clearly hear the instructions to air carrier Y -- whether cleared to cross or hold short of the runway our runway -- than to hear a computer voice announce the runway that we already knew we were on. Only when air carrier Y actually crossed our runway were we sure that they had actually been cleared to cross. Had tower actually told them to hold short and cleared us for takeoff prior to that; we would have been forced to ask for confirmation that air carrier Y was going to hold short -- we were unable to hear their clearance due to interference from raas. Immediately remove the current raas. Re-install only if it is upgraded with a crew-selectable inhibit function.
Original NASA ASRS Text
Title: AN ACR PILOT DISCUSSES THE LOUD AND UNNECESSARY RAAS WARNING AS THE CREW LINES UP ON THE DEPARTING RWY TO HOLD FOR CROSSING TFC.
Narrative: WE WERE CLEARED POSITION AND HOLD ON RWY 16 LEFT AT SEA. AS WE ALIGNED WITH THE RUNWAY THE RAAS SYSTEM ANNOUNCED 'ON RWY 16 LEFT' AT THE SAME TIME THAT TOWER ISSUED INSTRUCTIONS TO AN ACR Y FLIGHT EXITING RWY 16 CENTER DOWN FIELD. WE HAD A MUCH GREATER NEED TO CLEARLY HEAR THE INSTRUCTIONS TO ACR Y -- WHETHER CLEARED TO CROSS OR HOLD SHORT OF THE RUNWAY OUR RWY -- THAN TO HEAR A COMPUTER VOICE ANNOUNCE THE RWY THAT WE ALREADY KNEW WE WERE ON. ONLY WHEN ACR Y ACTUALLY CROSSED OUR RWY WERE WE SURE THAT THEY HAD ACTUALLY BEEN CLEARED TO CROSS. HAD TOWER ACTUALLY TOLD THEM TO HOLD SHORT AND CLEARED US FOR TAKEOFF PRIOR TO THAT; WE WOULD HAVE BEEN FORCED TO ASK FOR CONFIRMATION THAT ACR Y WAS GOING TO HOLD SHORT -- WE WERE UNABLE TO HEAR THEIR CLEARANCE DUE TO INTERFERENCE FROM RAAS. IMMEDIATELY REMOVE THE CURRENT RAAS. RE-INSTALL ONLY IF IT IS UPGRADED WITH A CREW-SELECTABLE INHIBIT FUNCTION.
Data retrieved from NASA's ASRS site as of May 2009 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.