FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN23LA297 · Cirrus Design Corp SR22

11 Jul 2023 · Boelus, NE, United States

Cirrus Design Corp SR22 · Accident en route

From Werner Ranch Airfield (NE36) to Central Nebraska Regional Airport (GRI)

Report a problem

Event

NTSB case
CEN23LA297
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
Event fatalities
Unknown
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
N151SR
Operator
Unknown
Onboard fatalities
Unknown
Route
From Werner Ranch Airfield (NE36), Anselmo, NETo Central Nebraska Regional Airport (GRI), Grand Island, NE
Aircraft age
About 17 years (built 2006)
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
En route · cruise
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
Unknown or undetermined
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

  • Not determined › Not determined

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot stated that the preflight inspection and engine runup revealed no anomalies and the takeoff, climb, and initial portion of cruise were routine. He noted that the engine missed briefly about halfway through the flight. However, as the flight progressed, the engine sputtered briefly and then lost power completely, although the propeller continued to windmill. The pilot reported he cycled the ignition thinking that the issue might be ignition related since it had been recently serviced. He recalled that the engine stopped just after he turned off the left magneto and did not restart when it was switched back on. He added that the right magneto shut down briefly. He activated the fuel boost pump and switched fuel tanks but his efforts to restore engine power were not successful. The pilot activated the airframe parachute, and the airplane touched down in a corn field.

Engine data recovered from the onboard avionics appeared stable throughout the flight until about 70 seconds before the accident. At that time, the engine fuel flow decreased to zero over a 26-second interval. The exhaust gas temperatures also began to decrease. Then, about 54 seconds before the accident, the engine speed began to decrease from 2,600 rpm until it reached 1,360 rpm.

During the postaccident examination, no anomalies with respect to the airframe or engine fuel systems was observed and, according to recovery personnel, both fuel tanks contained useable fuel.

The airplane was equipped with dual electronic ignition systems. The postaccident examination revealed that the fuse powering the right ignition controller module was open, which rendered the right ignition system inoperative. No preimpact anomalies were observed with respect to the left ignition system, nor any anomalies with respect to the fuel system or the engine assembly itself.

The investigation was unable to determine exactly why the engine missed during the flight or why the fuse was tripped. One possibility is that the engine missed when the fuse tripped, and the right ignition system became inoperative. At that point, the engine continued to operate on the remaining ignition system. When the pilot cycled off the left ignition system to troubleshoot the cause of the engine miss, he inadvertently shut off the only remaining ignition system, resulting in a total loss of engine power.

The pilot’s attempt to determine if the anomaly was ignition system related by isolating one system and then the other was reasonable. Because the ignition system fuses were installed behind the cockpit circuit breaker panel, the pilot was unable to detect the tripped fuse and determine that the right ignition system was inoperative. However, the engine should have been able to operate on the left ignition system.

Ultimately, the reason for the loss of engine power could not be determined.

Probable cause

Loss of engine power for reasons that could not be determined.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN23LA297
Event ID
20230712192609
Case number
CEN23LA297
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: local date, investigation status, coordinates, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2023-07-12.
  • API snapshot SHA-256: 8f804b6d0e2e4b3f4439b78b96d1835192ee4c86b5bb2a18228ce91a7c25208f; retrieved 2026-09-16T17:50:59.997Z.