20040102000539A

Accident · Substantial damage

FAA accident report · Piper PA-32RT-300 · Indianapolis, IN · January 2, 2004

Date
January 2, 2004 · 14:23 local
Place
Indianapolis, IN
Airport
Metropolitan Airport
Phase of flight
Final Approach
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N21992
NTSB investigation
NTSBCHI04LA052
Reported as
Piper PA32RT300
Reported engine
Lycoming IO540*
People aboard
4
Fatal injuries
0
Pilot’s flight hours
1,320 total863 in this make and model20 in the last 90 days

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.

(-23) The pilot was conducting an IFR approach to runway 33 at Indianapolis metro airport circle to land on runway 15. During the circle approach the left wing of Piper (N21992) made contact with trees causing substantial damage to the aircraft. The aircraft made a successful landing on runway 15 at (ump) Indianapolis metro airport.

As the FAA filed it

(-23) THE PILOT WAS CONDUCTING AN IFR APPROACH TO RUNWAY 33 AT INDIANAPOLIS METRO AIRPORT CIRCLE TO LAND ON RUNWAY 15. DURING THE CIRCLE APPROACH THE LEFT WING OF PIPER (N21992) MADE CONTACT WITH TREES CAUSING SUBSTANTIAL DAMAGE TO THE AIRCRAFT. THE AIRCRAFT MADE A SUCCESSFUL LANDING ON RUNWAY 15 AT (UMP) INDIANAPOLIS METRO AIRPORT.

NTSB investigation

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

Other reports on N21992 · 1

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