37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1199263 |
Time | |
Date | 201408 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | OMA.Airport |
State Reference | NE |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 3 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Ground Incursion Runway |
Narrative:
I took the local control position in a north configuration. Due to storms south of the field along final and winds favoring a south flow I decided to change to a south flow. I coordinated this change after aircraft X. There had been a bird strike prior to me taking the position. When we notified the airport of the bird strike they did not close the runway; they only said they would go out and search. The previous controller had advised two aircraft that there was a bird strike on 32L and if they still wanted to land. The visibility was 1 3/4 we couldn't switch them to the parallel. A operations vehicle came out and I was getting an aircraft off the runway. The incoming controller in charge asked me what [the operations vehicle] was doing. I looked and saw the vehicle on the runway with an aircraft on a two mile final. I sent the aircraft around. The confusion was around whether the runway was closed and it is the airports call to close the runway. The ground controller thought the runway was closed and allowed city operations onto the runway. When I realized city operations was on the runway I looked at the rid and placard and I had both in possession. To avoid further confusion put something in writing in the SOP.
Original NASA ASRS Text
Title: OMA Tower Controller reports of a bird strike; calls city operations out to take a look. Controller never clears city operations vehicle onto runway and an aircraft is on short final. Controller sends aircraft around.
Narrative: I took the local control position in a north configuration. Due to storms south of the field along final and winds favoring a south flow I decided to change to a south flow. I coordinated this change after Aircraft X. There had been a bird strike prior to me taking the position. When we notified the airport of the bird strike they did not close the runway; they only said they would go out and search. The previous controller had advised two aircraft that there was a bird strike on 32L and if they still wanted to land. The visibility was 1 3/4 we couldn't switch them to the parallel. A Operations vehicle came out and I was getting an aircraft off the runway. The incoming CIC asked me what [the operations vehicle] was doing. I looked and saw the vehicle on the runway with an aircraft on a two mile final. I sent the aircraft around. The confusion was around whether the runway was closed and it is the airports call to close the runway. The ground controller thought the runway was closed and allowed city operations onto the runway. When I realized city operations was on the runway I looked at the RID and placard and I had both in possession. To avoid further confusion put something in writing in the SOP.
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.