 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot of a mitsubishi MU2B 60 marquise (MU26) took evasive action on takeoff roll by moving over on the runway to avoid a mig 17 holding on the uncontrolled airport runway. The mig had landed several mins earlier but had not announced his intentions to back taxi to parking as was required due to the only taxiway being closed for construction.
| Attributes | |
| ACN | 414730 |
| Time | |
| Date | 199809 |
| Day | Tue |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | atc facility : dro airport : pro |
| State Reference | CO |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | general aviation : corporate |
| Make Model Name | MU-2B 60 Marquise |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : takeoff |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | general aviation : corporate |
| Make Model Name | Fighter |
| Operating Under FAR Part | Part 91 |
| Flight Phase | ground : holding ground other : taxi |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 120 flight time total : 7200 flight time type : 25 |
| ASRS Report | 414730 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : commercial pilot : instrument |
| Events | |
| Anomaly | conflict : ground critical non adherence : far other anomaly other |
| Independent Detector | other flight crewa other other : unspecified |
| Resolutory Action | flight crew : took evasive action |
| Consequence | Other |
| Miss Distance | horizontal : 25 vertical : 0 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
As I taxied north for a departure on runway 20, I observed 8 F16's ahead of me for taxi and departure. They took off in approximately 30 second intervals and turned to 'form up' northwest of the airport. They announced their intentions. They were going to make a low formation pass heading east, directly over the airport, then make a right 270 degree turn, fly down the runway and proceed north out of the area. As the last F16 departed and 'lead' announced their intentions, a MIG17 radioed that he would like to land on runway 20, which he did. A dornier 328 announced 'long final' for runway 20. I called the airliner and advised them that I would be holding short, which they acknowledged. The airliner touched down and on rollout announced that he would back-taxi to the 'turnoff' near the terminal -- which was about 2000 ft south of where I was holding. When he (during his back-taxi) arrived in the vicinity of his exit point, I announced that I was taking position on runway 20 and that I would hold position until the airliner was clear. At that point I announced that I was beginning my takeoff roll on runway 20. As I reached about 80 KTS, the MIG17 came into view. He was just left of (his left) centerline taxiing north. Insufficient distance perceived between him and me for a successful abort. I moved left of centerline about 30-40 ft and rotated about 2-3 seconds after passing by the mig which now appeared to be stopped. I never received any transmission from the mig pilot. It appears to me that 3 separate factors were significant in causing this event. First, traffic on either end was not visible from the opposite end due to runway topography. Second, the taxiway was closed for construction. Third, there was no positive control of aircraft. Airshows, airliners, and uncontrolled fields are a dangerous combination.
Original NASA ASRS Text
Title: PLT OF A MITSUBISHI MU2B 60 MARQUISE (MU26) TOOK EVASIVE ACTION ON TKOF ROLL BY MOVING OVER ON THE RWY TO AVOID A MIG 17 HOLDING ON THE UNCTLED ARPT RWY. THE MIG HAD LANDED SEVERAL MINS EARLIER BUT HAD NOT ANNOUNCED HIS INTENTIONS TO BACK TAXI TO PARKING AS WAS REQUIRED DUE TO THE ONLY TXWY BEING CLOSED FOR CONSTRUCTION.
Narrative: AS I TAXIED N FOR A DEP ON RWY 20, I OBSERVED 8 F16'S AHEAD OF ME FOR TAXI AND DEP. THEY TOOK OFF IN APPROX 30 SECOND INTERVALS AND TURNED TO 'FORM UP' NW OF THE ARPT. THEY ANNOUNCED THEIR INTENTIONS. THEY WERE GOING TO MAKE A LOW FORMATION PASS HDG E, DIRECTLY OVER THE ARPT, THEN MAKE A R 270 DEG TURN, FLY DOWN THE RWY AND PROCEED N OUT OF THE AREA. AS THE LAST F16 DEPARTED AND 'LEAD' ANNOUNCED THEIR INTENTIONS, A MIG17 RADIOED THAT HE WOULD LIKE TO LAND ON RWY 20, WHICH HE DID. A DORNIER 328 ANNOUNCED 'LONG FINAL' FOR RWY 20. I CALLED THE AIRLINER AND ADVISED THEM THAT I WOULD BE HOLDING SHORT, WHICH THEY ACKNOWLEDGED. THE AIRLINER TOUCHED DOWN AND ON ROLLOUT ANNOUNCED THAT HE WOULD BACK-TAXI TO THE 'TURNOFF' NEAR THE TERMINAL -- WHICH WAS ABOUT 2000 FT S OF WHERE I WAS HOLDING. WHEN HE (DURING HIS BACK-TAXI) ARRIVED IN THE VICINITY OF HIS EXIT POINT, I ANNOUNCED THAT I WAS TAKING POS ON RWY 20 AND THAT I WOULD HOLD POS UNTIL THE AIRLINER WAS CLR. AT THAT POINT I ANNOUNCED THAT I WAS BEGINNING MY TKOF ROLL ON RWY 20. AS I REACHED ABOUT 80 KTS, THE MIG17 CAME INTO VIEW. HE WAS JUST L OF (HIS L) CTRLINE TAXIING N. INSUFFICIENT DISTANCE PERCEIVED BTWN HIM AND ME FOR A SUCCESSFUL ABORT. I MOVED L OF CTRLINE ABOUT 30-40 FT AND ROTATED ABOUT 2-3 SECONDS AFTER PASSING BY THE MIG WHICH NOW APPEARED TO BE STOPPED. I NEVER RECEIVED ANY XMISSION FROM THE MIG PLT. IT APPEARS TO ME THAT 3 SEPARATE FACTORS WERE SIGNIFICANT IN CAUSING THIS EVENT. FIRST, TFC ON EITHER END WAS NOT VISIBLE FROM THE OPPOSITE END DUE TO RWY TOPOGRAPHY. SECOND, THE TXWY WAS CLOSED FOR CONSTRUCTION. THIRD, THERE WAS NO POSITIVE CTL OF ACFT. AIRSHOWS, AIRLINERS, AND UNCTLED FIELDS ARE A DANGEROUS COMBINATION.
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.