19960511046492A

Accident · Minor damage

FAA accident report · Sukhoi SU-29 · Denver, CO · May 11, 1996

Date: May 11, 1996 · 11:34 local
Place: Denver, CO
Airport: Centennial Airport
Phase of flight: Level Off Touchdown
Operating rules: General operating rules (Part 91)
Collision: Midair collision, second aircraft
Damage: Minor damage
Aircraft: N55SU
NTSB investigation: NTSBFTW96FA208
Reported as: Sukhoi SU29
Reported engine: VEDENY M14P
People aboard: 1
Fatal injuries: 0
Pilot’s flight hours: 21,000 total35 in this make and model25 in the last 90 days

N55SURegistration cancelled Oct 9, 2014 · Sukhoi SU-29S/N 73-05 Airframe modelSukhoi SU-29

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(.4) The pilot of the RV-4, N44AZ, had made initial contact with the control tower on the west arrival frequency, and was instructed to report entering a right downwind for runway 17R, which he acknowledged. At about the same time, the pilot of the Sukhoi SU-29, N55SU, made initial contact with the control tower on the east arrival frequency and was instructed to report on a left base for runway 17L. Both pilots were subsequently cleared to land on their respective runways. Instead of landing on his assigned runway 17R, the pilot of the RV-4 landed on 17L. The SU-29 then landed on top of the RV-4. The faa's ATC handbook advises controllers to restate the landing runway whenever there is a possibilty of a conflict with another aircraft which is using or planning to use another runway. The threshold of runway 17R is 1,800 feet beyond the threshold of runway 17L. The airport was hosting an open house at the time, and airborne flights from a 'parade of flight' were in progress.

As the FAA filed it

(.4) THE PILOT OF THE RV-4, N44AZ, HAD MADE INITIAL CONTACT WITH THE CONTROL TOWER ON THE WEST ARRIVAL FREQUENCY, AND WAS INSTRUCTED TO REPORT ENTERING A RIGHT DOWNWIND FOR RUNWAY 17R, WHICH HE ACKNOWLEDGED. AT ABOUT THE SAME TIME, THE PILOT OF THE SUKHOI SU-29, N55SU, MADE INITIAL CONTACT WITH THE CONTROL TOWER ON THE EAST ARRIVAL FREQUENCY AND WAS INSTRUCTED TO REPORT ON A LEFT BASE FOR RUNWAY 17L. BOTH PILOTS WERE SUBSEQUENTLY CLEARED TO LAND ON THEIR RESPECTIVE RUNWAYS. INSTEAD OF LANDING ON HIS ASSIGNED RUNWAY 17R, THE PILOT OF THE RV-4 LANDED ON 17L. THE SU-29 THEN LANDED ON TOP OF THE RV-4. THE FAA'S ATC HANDBOOK ADVISES CONTROLLERS TO RESTATE THE LANDING RUNWAY WHENEVER THERE IS A POSSIBILTY OF A CONFLICT WITH ANOTHER AIRCRAFT WHICH IS USING OR PLANNING TO USE ANOTHER RUNWAY. THE THRESHOLD OF RUNWAY 17R IS 1,800 FEET BEYOND THE THRESHOLD OF RUNWAY 17L. THE AIRPORT WAS HOSTING AN OPEN HOUSE AT THE TIME, AND AIRBORNE FLIGHTS FROM A 'PARADE OF FLIGHT' WERE IN PROGRESS.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.

NTSB FTW96FA208Accident · 1 fatalField investigationFinal reportEnglewood, COfailure of the pilot of the RV-4, N44AZ, to comply with an ATC clearance by landing on the wrong runway, and the failure of the pilot of the SU-29, N55SU, to maintain an adequate visual lookout. Factors in the accident were: the failure of the air traffic…May 11, 1996 · 2 aircraft · Minor damage

Other reports on N55SU · 1

Matched to the same aircraft by N-number and date.

Accident 20000815027019ALongmont, CO(-23)"Pilot reported that shortly after touchdown, the airplane swerved to the right and exited the runway. Postaccident examination by russian aviation experts, on December 11, 2000, determined that several structural members just aft of the engine firewall…Aug 15, 2000 · No damage