37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 751154 |
Time | |
Date | 200708 |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC Marginal |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | ground : takeoff roll |
Person 1 | |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : multi engine pilot : instrument pilot : cfi pilot : commercial pilot : flight engineer technician : airframe technician : powerplant |
Experience | flight time last 90 days : 120 flight time total : 17000 flight time type : 4000 |
ASRS Report | 751154 |
Events | |
Anomaly | aircraft equipment problem : less severe |
Independent Detector | other flight crewa |
Resolutory Action | none taken : unable |
Supplementary | |
Problem Areas | Aircraft |
Primary Problem | Aircraft |
Narrative:
This is the first operational raas aircraft that my air carrier has provided myself and my crew in my 12 years as a captain on this airbus fleet. While the importance of preventing both taxiway and runway incursions has been a major part of my ground operations briefings; the addition of the runway awareness and advisory system is; potentially; a welcome enhancement to the prevention of these incursions. The problem on this day was an inappropriate and distracting announcement during the 75 to 90 knot phase of our takeoff roll. We began our takeoff roll on runway xy; and as we approached and ultimately crossed runway xx; the raas announced 'approaching runway xx.' as the 80 knot callout and check had just occurred; and the control tower was talking to another; taxiing aircraft; this inappropriate callout was distracting. Please investigate; and determine if this raas unit was certified to allow callouts such as this; or if this is a local problem; not common to all raas systems. If the vendor that supplied this unit; or if the installation or software load needs to be modified; then I would ask that those efforts be given a high priority. Meanwhile; notification by each airline operator to its crews would seem to be wise.
Original NASA ASRS Text
Title: A PILOT AT ZZZ REPORTS A RAAS RWY CROSSING ALERT FOR RWY XX ACTIVATED AT 70 - 90 KTS WHILE ON A RWY XY TKOF ROLL.
Narrative: THIS IS THE FIRST OPERATIONAL RAAS AIRCRAFT THAT MY ACR HAS PROVIDED MYSELF AND MY CREW IN MY 12 YEARS AS A CAPTAIN ON THIS AIRBUS FLEET. WHILE THE IMPORTANCE OF PREVENTING BOTH TAXIWAY AND RUNWAY INCURSIONS HAS BEEN A MAJOR PART OF MY GROUND OPS BRIEFINGS; THE ADDITION OF THE RUNWAY AWARENESS AND ADVISORY SYSTEM IS; POTENTIALLY; A WELCOME ENHANCEMENT TO THE PREVENTION OF THESE INCURSIONS. THE PROBLEM ON THIS DAY WAS AN INAPPROPRIATE AND DISTRACTING ANNOUNCEMENT DURING THE 75 TO 90 KNOT PHASE OF OUR TAKEOFF ROLL. WE BEGAN OUR TAKEOFF ROLL ON RUNWAY XY; AND AS WE APPROACHED AND ULTIMATELY CROSSED RUNWAY XX; THE RAAS ANNOUNCED 'APPROACHING RUNWAY XX.' AS THE 80 KNOT CALLOUT AND CHECK HAD JUST OCCURRED; AND THE CONTROL TOWER WAS TALKING TO ANOTHER; TAXIING AIRCRAFT; THIS INAPPROPRIATE CALLOUT WAS DISTRACTING. PLEASE INVESTIGATE; AND DETERMINE IF THIS RAAS UNIT WAS CERTIFIED TO ALLOW CALLOUTS SUCH AS THIS; OR IF THIS IS A LOCAL PROBLEM; NOT COMMON TO ALL RAAS SYSTEMS. IF THE VENDOR THAT SUPPLIED THIS UNIT; OR IF THE INSTALLATION OR SOFTWARE LOAD NEEDS TO BE MODIFIED; THEN I WOULD ASK THAT THOSE EFFORTS BE GIVEN A HIGH PRIORITY. MEANWHILE; NOTIFICATION BY EACH AIRLINE OPERATOR TO ITS CREWS WOULD SEEM TO BE WISE.
Data retrieved from NASA's ASRS site as of January 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.