The U.S. aircraft register, updated daily
Accidents · NTSB ERA17FA167 · Final report

Cirrus Design CORP SR22 accident near Wallingford, Connecticut, April 24, 2017

On April 24, 2017 at about 10:25 pm local time, a 2005 Cirrus Design CORP SR22, registered N94LP, was destroyed in an accident during landing (flare/touchdown) near Wallingford, Connecticut (Meriden Markham Muni airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed and 1 person was seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's unstablilized approach and improper landing flare, which resulted in a bounced landing, and his subsequent failure to maintain control during a go-around. Contributing to the accident was the pilot's lack of experience in the accident airplane make and model.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
April 24, 2017 · about 10:25 pm local time
Place
Wallingford, Connecticut · Meriden Markham Muni · map
Type
Accident
Injuries
1 person was killed and 1 person was seriously injured.
Weather
visual conditions (good weather)
Aircraft
Cirrus Design CORP SR22, built 2005
Registration
N94LP · no longer on the register · serial 1484
Damage
Destroyed
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The accident flight was the private pilot's first flight without a flight instructor in his recently purchased, high-performance airplane. The passenger reported that, following an uneventful local flight, he and the pilot returned to the airport for a full-stop landing. Witnesses reported that the airplane was high and fast during the landing approach, touched down about halfway down the 3,100-ft-long runway, and bounced about three times before conducting a go-around. The second landing approach appeared to be slower but was still high. The airplane flared about 10 ft above the runway then abruptly descended, again touching down about halfway down the runway. The passenger reported that the airplane bounced "a couple of times" and that the bounces were "pretty high." A witness stated that, after bouncing, the airplane's engine rpm increased and the airplane became airborne, pitching to an approximate 40° nose-up attitude. About 75 ft above the ground, the airplane entered a steep, left-turning descent that continued to ground contact; the airplane came to rest next to a road just outside airport property and was consumed by a postcrash fire. The witness accounts of the airplane approaching the runway fast and high and its touchdown point are consistent with the pilot's failure to fly a stabilized landing approach. This likely contributed to the airplane touching down on the nose landing gear first, as evidenced by the black tire marks in an S-shaped (sinusoidal) pattern co-located with white paint transfer marks on the surface of the runway, which are consistent with a nosewheel shimmy and nosewheel pant contact. After bouncing during the second landing, the pilot added engine power to conduct a go-around, allowed the airplane's pitch to rapidly increase, and entered a steep left turn before attaining a proper climb speed, which resulted in a loss of control during the attempted go-around. Examination of the wreckage revealed no evidence of any preimpact failures or malfunctions of the airplane or engine that would have precluded normal operation. The pilot had about 1,200 total hours of flight experience and had received about 10.5 hours of transition training in the accident airplane make and model from a local flight instructor. During that time, the pilot performed 12 landings and received an endorsement for operating high-performance airplanes such as the accident airplane. Before purchasing the accident airplane, the pilot owned another airplane that was not classified as high-performance. Despite receiving transition training, it is likely that the pilot's lack of experience with his new airplane and its flight characteristics, and particularly operation of the airplane in abnormal/emergency situations, contributed to his loss of control.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Abnormal runway contact during landing (flare/touchdown) defining event
  2. Abrupt maneuver during landing (aborted after touchdown)
  3. Abrupt maneuver during takeoff
  4. Loss of control in flight during initial climb
  5. Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
  6. Fire/smoke (post-impact) during post (impact)

The NTSB's findings

  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Descent/approach/glide path › Not attained/maintained
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Airspeed › Not attained/maintained
  • cause Personnel issues › Task performance › Use of equip/info › Aircraft control › Pilot
  • factor Personnel issues › Experience/knowledge › Experience/qualifications › Total experience w/ equipment › Pilot

Pilot

  • Certificate: private
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 1,217 hours in all; 10.1 in this make and model; 10.1 in the last 90 days; 8.3 in the last 30 days; 1,139.4 as pilot in command
  • Last flight review: October 30, 2014
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 1,229 hours
  • Last inspection: annual inspection, March 13, 2017
  • Maximum gross weight: 3,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Cont Motor IO-550-N27B (piston); 1,229 hours total
  • Fire on the ground

The flight

  • Departed from: MMK Wallingford CT at 9:40 pm
  • Destination: MMK Wallingford CT
  • Flight plan: none
  • Runway 18, 3,100 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 180° at 5 knots
  • Visibility: 10 statute miles
  • Sky: overcast at 12,000 ft; a few clouds at 300 ft
  • Temperature: 61°F (16°C), dew point 36°F (2°C)
  • Altimeter: 30.14 inHg
  • Observation at 10:33 pm from MMK

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

13 documents, released by the NTSB on September 19, 2019. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.