FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22LA187 · Lancair IV P

10 Apr 2022 · Leicester, MA, United States

Lancair IV P · Accident: part(s) separation from aircraft en route

From Auburn Lewiston Municipal Airport (LEW) to Jacksonville Executive at Craig Airport (CRG)

Report a problem

Event

NTSB case
ERA22LA187
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
0 · all aircraft and ground
Ground fatalities
0
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

Lancair IV P

Aircraft type
Lancair IV
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
N7KJ
Operator
Unknown
Onboard fatalities
Unknown
Route
From Auburn Lewiston Municipal Airport (LEW), Lewiston, METo Jacksonville Executive at Craig Airport (CRG), Jacksonville, FL
Aircraft age
About 28 years (built 1994)
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
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
Part(s) separation from aircraft
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

  • Aircraft › Aircraft structures
  • 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

While en route the pilot reported there was a sudden explosion and the right window and portion of the right roof separated from the airplane. He performed an emergency descent and landed uneventfully.

The airplane was initially documented but was repaired before a detailed postaccident examination could be completed. The airframe could not be examined, and the separated window was not located; therefore, the reason for the separation could not be determined.

Probable cause

A separation of the window from the airframe for undetermined reasons.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22LA187
Event ID
20220412104933
Case number
ERA22LA187
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, cause areas. 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: 9891c012dc69d707f0b4f1086ea6d4204ee2d16124c155d2d1fb8f6d0090ca9b; retrieved 2026-09-16T15:07:38.482Z.