 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
DC3 has engine failure on takeoff roll, rejects takeoff, leaves runway, enters ramp and ground loops to avoid collision with a taxiing aircraft.
| Attributes | |
| ACN | 481176 |
| Time | |
| Date | 200006 |
| Day | Tue |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : buf.airport |
| State Reference | NY |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | general aviation : corporate |
| Make Model Name | DC-3/Dakota/Skytrain |
| Operating Under FAR Part | Part 91 |
| Flight Phase | ground : takeoff roll |
| Flight Plan | IFR |
| Aircraft 2 | |
| Controlling Facilities | tower : buf.tower |
| Operator | common carrier : air carrier |
| Make Model Name | Jetstream 32 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | ground : taxi |
| Flight Plan | None |
| Person 1 | |
| Affiliation | government : faa |
| Function | controller : ground controller : local |
| Qualification | controller : radar |
| Experience | controller radar : 18 |
| ASRS Report | 481176 |
| Person 2 | |
| Affiliation | company : corporate |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | aircraft equipment problem : critical conflict : ground critical excursion : runway incursion : taxiway other anomaly |
| Independent Detector | other controllera |
| Resolutory Action | flight crew : rejected takeoff flight crew : took evasive action other |
| Consequence | other other |
| Miss Distance | horizontal : 10 |
| Supplementary | |
| Problem Areas | ATC Facility Aircraft Flight Crew Human Performance ATC Human Performance |
| Primary Problem | Aircraft |
| Situations | |
| ATC Facility | procedure or policy : buf.tower staffing : buf.tower |
Narrative:
Aircraft Z, an A320, had just exited runway 23 at taxiway G and was holding on taxiway a waiting for aircraft Y to reposition from his gate to another one. Aircraft X, a DC3, was cleared for takeoff and rolling on runway 23. Aircraft X lost left engine on takeoff roll and exited runway 23 at taxiway east, basically out of control. He saw aircraft Z, facing him opposite direction on taxiway a and veered to avoid him. This put him on collision course with aircraft Y, who was just starting to taxi. Aircraft X spun around to avoid aircraft Y and stopped approximately 10 ft from him. I found this out later from the pilots, this area of ramp is not visible from the tower. I called airport crash fire rescue when I observed aircraft X leaving the runway. The dispatcher was inexperienced and slow to acknowledge. By the time crash fire rescue had responded and was approaching the runway to cross, the aircraft X pilot stated he was ok and wanted to taxi back to his ramp. I approved the taxi, advised crash fire rescue they were not needed, and had a field truck check the runway for FOD. The pilot of the aircraft Y was surprised by this and explained how close aircraft X had come to him. In hindsight, he was correct. I should have kept aircraft X where he was and had crash fire rescue inspect the aircraft. At the time I didn't know how close it was and I was trying to get aircraft X to his gate. After talking to aircraft Y pilot, I requested relief from position. It was over 1 hour before relief was finally provided. As the proximity sunk in, I think my performance suffered. Relief was available and should have been provided sooner.
Original NASA ASRS Text
Title: DC3 HAS ENG FAILURE ON TKOF ROLL, REJECTS TKOF, LEAVES RWY, ENTERS RAMP AND GND LOOPS TO AVOID COLLISION WITH A TAXIING ACFT.
Narrative: ACFT Z, AN A320, HAD JUST EXITED RWY 23 AT TXWY G AND WAS HOLDING ON TXWY A WAITING FOR ACFT Y TO REPOSITION FROM HIS GATE TO ANOTHER ONE. ACFT X, A DC3, WAS CLRED FOR TKOF AND ROLLING ON RWY 23. ACFT X LOST L ENG ON TKOF ROLL AND EXITED RWY 23 AT TXWY E, BASICALLY OUT OF CTL. HE SAW ACFT Z, FACING HIM OPPOSITE DIRECTION ON TXWY A AND VEERED TO AVOID HIM. THIS PUT HIM ON COLLISION COURSE WITH ACFT Y, WHO WAS JUST STARTING TO TAXI. ACFT X SPUN AROUND TO AVOID ACFT Y AND STOPPED APPROX 10 FT FROM HIM. I FOUND THIS OUT LATER FROM THE PLTS, THIS AREA OF RAMP IS NOT VISIBLE FROM THE TWR. I CALLED ARPT CRASH FIRE RESCUE WHEN I OBSERVED ACFT X LEAVING THE RWY. THE DISPATCHER WAS INEXPERIENCED AND SLOW TO ACKNOWLEDGE. BY THE TIME CRASH FIRE RESCUE HAD RESPONDED AND WAS APCHING THE RWY TO CROSS, THE ACFT X PLT STATED HE WAS OK AND WANTED TO TAXI BACK TO HIS RAMP. I APPROVED THE TAXI, ADVISED CRASH FIRE RESCUE THEY WERE NOT NEEDED, AND HAD A FIELD TRUCK CHK THE RWY FOR FOD. THE PLT OF THE ACFT Y WAS SURPRISED BY THIS AND EXPLAINED HOW CLOSE ACFT X HAD COME TO HIM. IN HINDSIGHT, HE WAS CORRECT. I SHOULD HAVE KEPT ACFT X WHERE HE WAS AND HAD CRASH FIRE RESCUE INSPECT THE ACFT. AT THE TIME I DIDN'T KNOW HOW CLOSE IT WAS AND I WAS TRYING TO GET ACFT X TO HIS GATE. AFTER TALKING TO ACFT Y PLT, I REQUESTED RELIEF FROM POS. IT WAS OVER 1 HR BEFORE RELIEF WAS FINALLY PROVIDED. AS THE PROX SUNK IN, I THINK MY PERFORMANCE SUFFERED. RELIEF WAS AVAILABLE AND SHOULD HAVE BEEN PROVIDED SOONER.
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.