20030702016539A

Accident · Destroyed

FAA accident report · Amtr Dragonflmkii · Minneapolis, MN · July 2, 2003

Date
July 2, 2003 · 21:42 local
Place
Minneapolis, MN
Airport
Flying Cloud Airport
Phase of flight
Forced/Precautionary Landing
Operating rules
General operating rules (Part 91)
Damage
Destroyed
Aircraft
N25JD
NTSB investigation
NTSBCHI03LA192
Reported as
Amtr Dragonflmkii
Reported engine
AMTRVW VW2100VOLKS
Fatal injuries
0
Pilot’s flight hours
79 total22 in this make and model34 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) Aircraft departed runway 18 at fcm and was observed by ATC in a minimal climb. When queried the pilot reported having engine problems. He stated that he would try and make it back to the field but did not think he could do so. Aircraft crashed in a wooded area 1.5 miles se of the airport. The pilot sustained serious injuries.

As the FAA filed it

(-23) AIRCRAFT DEPARTED RUNWAY 18 AT FCM AND WAS OBSERVED BY ATC IN A MINIMAL CLIMB. WHEN QUERIED THE PILOT REPORTED HAVING ENGINE PROBLEMS. HE STATED THAT HE WOULD TRY AND MAKE IT BACK TO THE FIELD BUT DID NOT THINK HE COULD DO SO. AIRCRAFT CRASHED IN A WOODED AREA 1.5 MILES SE OF THE AIRPORT. THE PILOT SUSTAINED SERIOUS INJURIES.

NTSB investigation

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