# Accident 19900614020099A: Amtr VK30, Baraboo, WI, June 14, 1990

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 14, 1990, 14:10 local time
- Place: Baraboo, WI
- Airport: Baraboo Wisconsin Dells
- Damage: Destroyed
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 43.4591° N, 89.7396° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=43.4591&lon=-89.7396&mi=10
- Aircraft: N888EK, a cancelled registration (https://openairdocs.org/deregistered/N888EK-1995-03-23) (OpenAirDocs)
- Registry model: Klapmeiesa A L/Klapmeiesa D E CIRRUS VK-30 (registry code 05616PF, https://openairdocs.org/model/klapmeiesa-a-l-klapmeiesa-d-e-cirrus-vk-30) (OpenAirDocs)
- Reported make and model: AMTR VK30
- Reported engine: AMTR BUICKV8
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 2,400 total, 250 in this make and model, 60 in the last 90 days
- NTSB investigation: [NTSB CHI90DEP05](https://openairdocs.org/ntsb/CHI90DEP05) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19900614020099A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

LOST POWER ON TAKEOFF AFTER ENGINE OVERHEATED. FIRE IN ENGINE. AIR INTAKE HAD COLLAPSED. LOOSE EXHAUST MANIFOLD.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CHI90DEP05](https://openairdocs.org/ntsb/CHI90DEP05), Jun 14, 1990: Cirrus Klappmeier Cirrus VF-30 (N888EK), Baraboo, WI, destroyed. Probable cause: MANUFACTURER'S INADEQUATE EQUIPMENT DESIGN TO PREVENT A FUEL LEAK WHICH RESULTED IN AN IN-FLIGHT FIRE. A FACTOR RELATED TO THE ACCIDENT WAS THE LACK OF AN UNSUITABLE FORCED LANDING AREA.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.