# Accident 20200809009879A: Piper PA-22-150, Burlington, WI, August 9, 2020

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: August 9, 2020, 14:40 local time
- Place: Burlington, WI
- Airport: Burlington Municipal
- Damage: Destroyed
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 42.6803° N, 88.3022° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=42.6803&lon=-88.3022&mi=10
- Aircraft: N6849B, registered now (https://openairdocs.org/aircraft/N6849B) (OpenAirDocs)
- Registry model: Piper PA-22-150 (registry code 7102210, https://openairdocs.org/model/piper-pa-22-150) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA-22-150
- Reported engine: LYCOMING 0-320 SERIES
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 2
- Pilot certificates: Private pilot
- Pilot flight hours: 1,400 total, 500 in this make and model, 4 in the last 90 days
- NTSB investigation: [NTSB CEN20LA329](https://openairdocs.org/ntsb/CEN20LA329) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20200809009879A

## Narrative

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

ON AUGUST 9, 2020 AT APPROXIMATELY 14:37 PM THE PIC DEPARTED BURLINGTON MUNICIPAL AIRPORT (KBUU)USING RUNWAY 19 A GRASS RUNWAY. THE PILOT SAID HE DID A NORMAL RUN UP AND EVERYTHING SEEMED FINE. HOWEVER HE DETERMINED THAT HE NEEDED TO USE FULL FLAPS AND SOFT FIELD PROCEDURES FOR THE TAKEOFF BECAUSE OF THE HIGH TEMPERATURE THAT DAY. HE INTENDED TO ACCELERATE IN GROUND EFFECT TO ATTAIN FLYING SPEED. DURING THE TAKEOFF ROLL HE NOTED THAT THE AIRCRAFT SEEMED "MUSHY" AND WAS SLOW TO ACCELERATE. HE SAID HE "YANKED" IT OFF THE GROUND TO ATTEMPT TO ACCELERATE IN GROUND EFFECT. THE AIRCRAFT REFUSED TO CLIMB NORMALLY BUT HE WAS ABLE TO GET IT HIGH ENOUGH TO MISS THE FIRST LINE OF TREES AHEAD. HE SAID THE AIRPLANE STOPPED CLIMBING BUT HE NEEDED TO AVOID ANOTHER AREA OF TREES AHEAD. IN MAKING A TURN TO AVOID THE TREES THE AIRPLANE STOPPED FLYING. IT STALLED AND FELL NOSE FIRST INTO THE GROUND LANDING IN A RESIDENTIAL AREA ON THE FRONT LAWN OF A HOUSE AT ^PRIVACY DATA OMITTED^. THE AIRCRAFT CAME TO REST INVERTED MISSING THE HOUSE. THE PILOT AND THE PASSENGER HAD SERIOUS INJURIES AND WERE TRANSPORTED BY FLIGHT FOR LIFE EMERGENCY HELICOPTER TO THE FROEDTERT HOSPITAL IN MILWAUKEE, WISCONSIN.

## 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 CEN20LA329](https://openairdocs.org/ntsb/CEN20LA329), Aug 9, 2020: Piper PA22 (N6849B), Burlington, WI, substantial damage. Probable cause: A partial loss of engine power due to the formation of carburetor ice while on the ground, which resulted in reduced climb capability and impact with trees during the initial climb.

## Other reports on N6849B (1)

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

- [Accident 20120305003459A](https://openairdocs.org/incident/20120305003459A), Mar 5, 2012: Piper PA-22-150 (N6849B), Mukwonago, WI, Substantial damage. March 5, 2012 at approximately 1417 local time N6849B a 1956 Piper PA-22-150 enroute from ephraim Wisconsin (3D2) to burlington Wisconsin (buu) experienced a…

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.
