# Accident 20210422005509A: Piper Aircraft Inc PA-28-181, Faribault, MN, April 22, 2021

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 22, 2021, 14:10 local time
- Place: Faribault, MN
- Airport: Faribault Municipal
- Damage: Substantial damage
- Phase of flight: Takeoff: Climb Out
- Operating rules: General operating rules (Part 91)
- Location: 44.3290° N, 93.3131° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=44.3290&lon=-93.3131&mi=10
- Aircraft: N7114C, registered now (https://openairdocs.org/aircraft/N7114C) (OpenAirDocs)
- Registry model: Piper PA-28-181 (registry code 7102832, https://openairdocs.org/model/piper-pa-28-181) (OpenAirDocs)
- Registry engine: Lycoming O-360-A4M (registry code 42276, https://openairdocs.org/engine/lycoming-o-360-a4m) (OpenAirDocs)
- Reported make and model: PIPER AIRCRAFT INC PA-28-181
- Reported engine: LYCOMING O-360-A4M
- People aboard: 2
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Commercial pilot, flight instructor, student
- Pilot flight hours: 710 total, 450 in this make and model, 90 in the last 90 days
- NTSB investigation: [NTSB CEN21LA197](https://openairdocs.org/ntsb/CEN21LA197) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20210422005509A

## Narrative

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

2021-04-22 N7114C FIRST FLIGHT WITH A NEW STUDENT PILOT WHILE PERFORMING TOUCH-N-GO?S AT KFBL, FARIBAULT STALLED AND LANDED IN A FARM FIELD APPROXIMATELY 1/3 MILE NORTHWEST OF RWY30.

THE CFI TOOK OFF FROM KFCM, HE KNEW THERE WAS GUSTY WINDS, BUT HEADED DOWN TO KFBL, FARIBAULT AIRPORT. HE SAID UP AT ALTITUDE HE THOUGHT THE SP WAS DOING A GOOD JOB MAINTAINING ALTITUDE AND PERFORMING TURNS. THEY PRESSED ON TO KFBL WHERE THE CFI DID A PATTERN/LANDING/TOUCH AND GO DEMO. HE THEN LET THE SP FLY THE PATTERN AND TOOK THE CONTROLS ON FINAL FOR THE LANDING. ON THE ROLLOUT HE HANDED THE CONTROLS TO THE SP TO COMPLETE A TOUCH AND GO TAKEOFF. THE CFI STATED HE DID HAVE TO TAKE THE CONTROLS IN THE CROSS WIND TURN, TAKE OUT SOME OF THE TURNING FORCES, BUILD AIRSPEED AND THEN GIVE CONTROLS BACK TO THE SP. THE CFI DID THE NEXT LANDING AND HANDED THE ROLLING AIRCRAFT CONTROLS TO THE STUDENT, WHEN THE STUDENT PULLED OFF THE GROUND THE AIRCRAFT NOSE WENT LEFT INTO THE WIND, TAIL RIGHT, AND IT STARTED HEADING LEFT TOWARD THE TREE LINE. THE CFI TOOK THE CONTROLS, REALIZED THE POWER WAS AT 2100 RPM VS AROUND 2600 RPM, SO HE ADDED FULL POWER AND PULLED AFT AS IMPACT WITH THE TREES BECAME IMMINENT. THERE WAS A THOUGHT THEY WOULD CLEAR THEM, BUT THEN THE TAIL HIT, THE AIRCRAFT PITCHED FORWARD AND THE CFI SAW THE GROUND, HE HELD THE NOSE DOWN, YELLED BRACE FOR IMPACT AND AT THE LAST SECOND, FIGURES ABOUT 10 FT, HE PULLED AFT AS HARD AS HE COULD. THEY IMPACTED AND STOPPED ALMOST INSTANTLY. HE SHUT DOWN, THEY BOTH WERE OK AND GOT OUT, AND EMERGENCY SERVICES WERE ARRIVING AS WITNESSES HAD ALREADY ACTIVATED THEM.

## 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 CEN21LA197](https://openairdocs.org/ntsb/CEN21LA197), Apr 22, 2021: Piper PA28 (N7114C), Faribault, MN, substantial damage. Probable cause: The student pilot’s failure to maintain control during takeoff in gusty wind conditions and the flight instructor’s delayed remedial action, which resulted in the airplane colliding with trees and…

## Other reports on N7114C (1)

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

- [Accident 20230123002009A](https://openairdocs.org/incident/20230123002009A), Jan 23, 2023: Piper Aircraft Inc PA-28-181 (N7114C), Eden Prairie, MN, Substantial damage. 01/23/2023 [privacy data omitted] went off left side of runway at flying cloud airport (kfcm) during attempted go around. No injuries, substantial damage.…

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.