37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1083432 |
Time | |
Date | 201304 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | PA-18/19 Super Cub |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Route In Use | None |
Flight Plan | VFR |
Person 1 | |
Function | Ground |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC |
Narrative:
I assumed ground control duties from an overwhelmed developmental controller recently certified on ground controller. High winds and wind shears had runway 34 in use. Traffic volume and complexity were extremely high with the short runway and a fly-in and heavy pattern traffic. Ground control had control of runway 7/25 from taxiway C to the east for crossing aircraft and vehicles. After relieving the other controller; I established a circuitous taxi route for the fly in flights taxiing out via taxiway K; crossing runway 7/25; and inbound taxiing via C; crossing runway 7/25. I worked this circuitous route for approximately 40-45 minutes. A PA18 was taxied to runway 7 at taxiway C for departure to alleviate workload for the local control. I released control of runway 7/25 to local control for the departure. I then; without thinking; issued instructions for the PA18 to cross runway 25 at taxiway K as I had been doing non-stop since assuming the position. I was informed later that local control had cleared the PA32 for take off runway 7; and he climbed out over the PA18 an estimated 100 ft-200 ft. No one; including myself; witnessed the event as all focus was on the 34 operation. I also experienced a loss of communications when my head set ptt failed during the transmission to the PA18. First; situational awareness! Secondly; [a controller needs] heightened awareness when giving/receiving control of a runway. Visual aids were in use but not used effectively.
Original NASA ASRS Text
Title: Ground Controller described a loss of runway separation event when crossing a runway with a departure taking off; the internal coordination failing between Ground Control and Local Control.
Narrative: I assumed Ground Control duties from an overwhelmed Developmental Controller recently certified on Ground Controller. High winds and wind shears had Runway 34 in use. Traffic volume and complexity were extremely high with the short runway and a fly-in and heavy pattern traffic. Ground Control had control of Runway 7/25 from Taxiway C to the east for crossing aircraft and vehicles. After relieving the other Controller; I established a circuitous taxi route for the fly in flights taxiing out via Taxiway K; crossing Runway 7/25; and inbound taxiing via C; crossing Runway 7/25. I worked this circuitous route for approximately 40-45 minutes. A PA18 was taxied to Runway 7 at Taxiway C for departure to alleviate workload for the Local Control. I released control of Runway 7/25 to Local Control for the departure. I then; without thinking; issued instructions for the PA18 to cross Runway 25 at Taxiway K as I had been doing non-stop since assuming the position. I was informed later that Local Control had cleared the PA32 for take off Runway 7; and he climbed out over the PA18 an estimated 100 FT-200 FT. No one; including myself; witnessed the event as all focus was on the 34 operation. I also experienced a loss of communications when my head set PTT failed during the transmission to the PA18. First; SITUATIONAL AWARENESS! Secondly; [a controller needs] heightened awareness when giving/receiving control of a runway. Visual aids were in use but not used effectively.
Data retrieved from NASA's ASRS site as of July 2013 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.