FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA12FA540 · Cirrus Design Corp SR22

1 Sept 2012 · Falmouth, MA, United States

Cirrus Design Corp SR22 · Accident: loss of control in flight during landing

From Tweed New Haven Airport (HVN) to Falmouth Airpark (5B6)

Report a problem

Event

NTSB case
ERA12FA540
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cirrus Design Corp SR22

Aircraft type
Cirrus SR22
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N221DV
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tweed New Haven Airport (HVN), New Haven, CTTo Falmouth Airpark (5B6), Falmouth, MA
Aircraft age
About 4 years (built 2008)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

During the cross-country instructional flight in the side-stick airplane, with the student pilot on the controls in the left seat and the flight instructor in the right seat, the airplane entered the landing pattern. During the final approach, witnesses saw the airplane drifting to the left while descending at a relatively high sink rate. Witnesses heard the power being adjusted, and, close to the ground, the engine went to high power. The airplane's nose rose, and the airplane veered to the left. The airplane touched down left wing down off the runway in grass, heading about 40 degrees left of the runway centerline. It then entered woods, where it hit numerous trees and came to rest upside down and on fire.

The student pilot stated that he thought the instructor was on the flight controls with him as had happened during previous flights. He also recalled the instructor pointing to the airspeed indicator on final approach and took it to mean that the airplane was slow. Although the instructor had previously used positive passing of controls on other flights, neither the student pilot nor the passenger recalled hearing him say anything during the final approach. The student pilot indicated that at some point he was not sure who was flying, although, after the accident, witnesses heard him saying multiple times that he was sorry he "did that."

Examination of the wreckage revealed no preexisting mechanical anomalies that would have precluded normal operation. Wind, as recorded at a nearby airport, was from slightly left of runway heading at 15 knots, gusting to 18 knots.

Five of the instructor's seven private pilot candidates failed their initial practical test, which went unnoticed by his flight school. However, none of the failures were due to poor landings, all the candidates passed on their second try, and all interviewed had positive words about the instructor. One of the instructor's previous students indicated that he had ridden the controls with her as well. The instructor had been known to work extra hours, but there was no evidence that he was fatigued during the flight. The instructor likely also had a discussion with a principal of the flight school that resulted in him arriving late for the flight, but there was no indication that it distracted him during the approach.

The instructor was responsible for the safety of the flight and, as such, should have effected positive remedial action before the student pilot was able to put the airplane in an unrecoverable position.

Probable cause

The flight instructor’s inadequate remedial action. Contributing to the accident was the student pilot’s poor control of the airplane during the approach.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA12FA540
Event ID
20120901X42234
Case number
ERA12FA540
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: cb0ccbc0eed0e87b50cdec692d64c0d2d2835a89522a081a0f7497858a7fb4f0; retrieved 2026-09-17T05:49:14.148Z.