Cirrus SR22 accident near Lowville, New York, April 8, 2018
On April 8, 2018 at about 8:53 pm local time, a 2003 Cirrus SR22, registered CGMDQ, was substantially damaged in an accident during enroute (cruise) near Lowville, New York. It was a personal flight under general aviation rules (Part 91). No one was hurt; 3 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilot's diverted attention, which resulted in his inadequate monitoring of the airplane's attitude and a loss of control in flight.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 8, 2018 · about 8:53 pm local time
- Place
- Lowville, New York · map
- Type
- Accident
- Injuries
- No one was hurt; 3 people were on board or involved.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Cirrus SR22, built 2003 · all SR22s on the register
- Registration
- CGMDQ · no longer on the register · serial 0654
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The airplane was on a cross-country flight at 9,000 ft mean sea level, which was about 1,000 ft above clouds. At that time, the private pilot had the autopilot engaged and in navigation mode for the airplane to proceed directly to the next waypoint. An air traffic controller requested that the pilot turn right 20° or more, which the pilot complied with by switching the autopilot to heading mode and selecting the desired heading. Subsequently, the controller advised the pilot that he could proceed back on course. The pilot switched the autopilot back to navigation mode but did not select the next waypoint on the GPS. He realized immediately that he was returning to his previous navigation course and then selected the next waypoint on the GPS and again selected navigation mode on the autopilot. By the time he returned his attention to the primary flight display, the airplane was descending out of control through clouds, and the pilot subsequently activated the airplane's parachute system. The airplane descended via parachute and landed upright in a field, but wind gusts blew the parachute, which inverted the airplane. Examination of the wreckage revealed that during the hard landing, the nose landing gear collapsed and both main landing gear spread outward, which resulted in substantial damage to the primary structure of the airplane. The primary flight display did not record any data. Thus, the investigation could not determine if the autopilot was engaged when the airplane departed controlled flight. However, regardless of whether or not the autopilot was engaged, it is likely that the pilot's attention was diverted to the GPS, which resulted in his failure to adequately monitor the airplane's attitude and maintain control of the airplane.
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
- Loss of control in flight during enroute (cruise) defining event
- Miscellaneous/other during uncontrolled descent
- Hard landing during landing
The NTSB's findings
- cause Personnel issues › Psychological › Attention/monitoring › Attention › Pilot
- cause Personnel issues › Psychological › Attention/monitoring › Monitoring equip/instruments › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 292 hours in all; 220 in this make and model; 19 in the last 90 days; 17 in the last 30 days; 124 as pilot in command
- Last flight review: November 1, 2017
- Medical certificate: Class 3 (without waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,706 hours
- Last inspection: annual inspection, February 5, 2018; 15 hours since
- Maximum gross weight: 3,400 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental IO-550-N (piston); 830 hours total
The flight
- Departed from: HMZ Bedord PA at 7:17 pm
- Destination: CYMX Mirabel
- Flight plan: IFR
Weather at the time
- Light: daylight
- Wind: from 310° at 3 knots
- Visibility: 1.4 statute miles
- Sky: broken clouds at 1,000 ft; a few clouds at 200 ft
- Temperature: 27°F (-3°C), dew point 21°F (-6°C)
- Altimeter: 29.92 inHg
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
6 documents, released by the NTSB on December 4, 2018. 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 12 pages | View Download |
| 2 | Interview Summary | PDF, 1 page | View Download |
| 3 | Weather Report | PDF, 1 page | View Download |
| 4 | Photo | PDF, 1 page | View Download |
| 5 | Statement of Party Representatives to NTSB Investigation | PDF, 10 pages | View Download |
| 6 | Evidence Control Form | PDF, 1 page | View Download |
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.