 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Ord controller described amass alarm event; allegedly caused by an arrival aircraft alarming on itself.
| Attributes | |
| ACN | 750257 |
| Time | |
| Date | 200708 |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : ord.airport |
| State Reference | IL |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | Marginal |
| Weather Elements | Rain Thunderstorm |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : ord.tower |
| Operator | common carrier : air carrier |
| Make Model Name | EMB ERJ 145 ER&LR |
| Operating Under FAR Part | Part 121 |
| Flight Phase | landing : go around landing : touch and go |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : local |
| Qualification | controller : radar |
| Experience | controller military : 4 controller radar : 8 |
| ASRS Report | 750257 |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | atc equipment other atc equipment : amass other controllera |
| Resolutory Action | flight crew : executed go around flight crew : took evasive action |
| Supplementary | |
| Problem Areas | Navigational Facility |
| Primary Problem | Navigational Facility |
Narrative:
While working south local control (landing runway 14R and departing runway 28) I was alerted by the amass safety logic function that runway 14R was occupied. I looked at the first arrival to ensure that wasn't the factor. It was not as that aircraft was clear of the runway. Without looking any further and not knowing what the conflict was; I sent the next arrival around. After I sent the arrival around I noticed that the aircraft had touched its main gear on the runway and pwred up and took off. After reviewing the amass data I was told that the arrival aircraft generated the alert on itself. So there was no conflict as indicated by the amass. By luck I did not have a runway 28 departure at the time as this false alert would have had the potential to cause a midair; the very thing this equipment is supposed to aid in preventing.
Original NASA ASRS Text
Title: ORD CTLR DESCRIBED AMASS ALARM EVENT; ALLEGEDLY CAUSED BY AN ARR ACFT ALARMING ON ITSELF.
Narrative: WHILE WORKING S LCL CTL (LNDG RWY 14R AND DEPARTING RWY 28) I WAS ALERTED BY THE AMASS SAFETY LOGIC FUNCTION THAT RWY 14R WAS OCCUPIED. I LOOKED AT THE FIRST ARR TO ENSURE THAT WASN'T THE FACTOR. IT WAS NOT AS THAT ACFT WAS CLR OF THE RWY. WITHOUT LOOKING ANY FURTHER AND NOT KNOWING WHAT THE CONFLICT WAS; I SENT THE NEXT ARR AROUND. AFTER I SENT THE ARR AROUND I NOTICED THAT THE ACFT HAD TOUCHED ITS MAIN GEAR ON THE RWY AND PWRED UP AND TOOK OFF. AFTER REVIEWING THE AMASS DATA I WAS TOLD THAT THE ARR ACFT GENERATED THE ALERT ON ITSELF. SO THERE WAS NO CONFLICT AS INDICATED BY THE AMASS. BY LUCK I DID NOT HAVE A RWY 28 DEP AT THE TIME AS THIS FALSE ALERT WOULD HAVE HAD THE POTENTIAL TO CAUSE A MIDAIR; THE VERY THING THIS EQUIP IS SUPPOSED TO AID IN PREVENTING.
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.