37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 476866 |
Time | |
Date | 200005 |
Day | Sat |
Local Time Of Day | 0001 To 0600 |
Place | |
Locale Reference | airport : mdw.airport |
State Reference | IL |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Controlling Facilities | tower : mdw.tower |
Operator | common carrier : air carrier |
Make Model Name | B727 Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Navigation In Use | Other |
Flight Phase | landing : go around |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Controlling Facilities | tower : mdw.tower |
Operator | general aviation : personal |
Make Model Name | Commander 500 |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : position and hold |
Flight Plan | VFR |
Person 1 | |
Function | controller : flight data controller : radar controller : supervisor controller : clearance delivery controller : combined local controller : combined ground |
Qualification | controller : radar |
ASRS Report | 476866 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | non adherence : published procedure non adherence : company policies |
Independent Detector | other controllera other flight crewa |
Resolutory Action | none taken : detected after the fact |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Operational Error |
Narrative:
I was working with 1 other controller who left the cabin attendant. All position were combined and I was signed on as controller in charge because I was the only one in the tower at that time. I was busy separating traffic on the ground, attending to paperwork that is completed on this shift. I have not been trained on how to do this task. Coordinating with chicago approach control when air carrier X initiated a go around because there was an aircraft on the runway. I knew a situation was arising and needed attention and action needed to be taken. I was aware of the aircraft holding in position and aware of the aircraft on final approach for runway 4 and knew evasive action needed to be taken to prevent loss of separation. I was distraction with duties of low priority and felt at the time when the pilot initiated the go around there was still enough time for me to issue the clearance, and I was about to do so, but the pilot beat me to it. It is a standard practice at mdw to depart an aircraft in a 3 mi gap. We are trained to do this. We allow minimum spacing for gars due to the short runways. It is not unusual to send an aircraft around at the last possible second before separation loss occurs. From what I saw, the aircraft was well above the tower and had ample lateral separation to execute a go around. An aircraft-initiated go around or controller-initiated go around is a common occurrence at mdw.
Original NASA ASRS Text
Title: B727 CREW ON FINAL TO MDW INITIATED A GAR DUE TO ACFT IN POS.
Narrative: I WAS WORKING WITH 1 OTHER CTLR WHO LEFT THE CAB. ALL POS WERE COMBINED AND I WAS SIGNED ON AS CIC BECAUSE I WAS THE ONLY ONE IN THE TWR AT THAT TIME. I WAS BUSY SEPARATING TFC ON THE GND, ATTENDING TO PAPERWORK THAT IS COMPLETED ON THIS SHIFT. I HAVE NOT BEEN TRAINED ON HOW TO DO THIS TASK. COORDINATING WITH CHICAGO APCH CTL WHEN ACR X INITIATED A GAR BECAUSE THERE WAS AN ACFT ON THE RWY. I KNEW A SIT WAS ARISING AND NEEDED ATTN AND ACTION NEEDED TO BE TAKEN. I WAS AWARE OF THE ACFT HOLDING IN POS AND AWARE OF THE ACFT ON FINAL APCH FOR RWY 4 AND KNEW EVASIVE ACTION NEEDED TO BE TAKEN TO PREVENT LOSS OF SEPARATION. I WAS DISTR WITH DUTIES OF LOW PRIORITY AND FELT AT THE TIME WHEN THE PLT INITIATED THE GAR THERE WAS STILL ENOUGH TIME FOR ME TO ISSUE THE CLRNC, AND I WAS ABOUT TO DO SO, BUT THE PLT BEAT ME TO IT. IT IS A STANDARD PRACTICE AT MDW TO DEPART AN ACFT IN A 3 MI GAP. WE ARE TRAINED TO DO THIS. WE ALLOW MINIMUM SPACING FOR GARS DUE TO THE SHORT RWYS. IT IS NOT UNUSUAL TO SEND AN ACFT AROUND AT THE LAST POSSIBLE SECOND BEFORE SEPARATION LOSS OCCURS. FROM WHAT I SAW, THE ACFT WAS WELL ABOVE THE TWR AND HAD AMPLE LATERAL SEPARATION TO EXECUTE A GAR. AN ACFT-INITIATED GAR OR CTLR-INITIATED GAR IS A COMMON OCCURRENCE AT MDW.
Data retrieved from NASA's ASRS site as of July 2007 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.