FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN21LA367 · Pulsar Sport 150

9 Aug 2021 · Osceola, WI, United States

Pulsar Sport 150 · Accident

Report a problem

Event

NTSB case
CEN21LA367
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

Pulsar Sport 150

Aircraft type
Pulsar Sport 150
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
N997EM
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 7 years (built 2014)
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
Unknown
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

No findings designated as a cause are recorded in the NTSB data yet.

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 completed one touch and go landing. During the climb the airplane’s engine lost total power. The pilot selected a field for a forced landing. During the forced landing the airplane impacted terrain and came to rest upright. The airplane sustained substantial damage when both wings separated from the fuselage during the forced landing.

The airplane was recovered, and the engine was examined. Impact damage to the carburetor prevented an engine test run. A visual inspection of the engine noted that a wire separated from the left magneto; however, it could not be determined if this was a result of the forced landing or if it had separated before the landing. The magneto was removed and tested by rotating the magneto with a drill; spark was observed on each terminal. The engine and fuel system examination did not reveal a reason for the loss of engine power.

Probable cause

The total loss of engine power for undermined reasons based on available information

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN21LA367
Event ID
20210810103666
Case number
CEN21LA367
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: 251ee842b547c4fe07a0b8217885a83cff617b73d2f7ed821af9f958c3110984; retrieved 2026-09-16T14:23:34.670Z.