WPR24FA156 · Extra Flugzeugbau Gmbh EA 300/L
Extra Flugzeugbau Gmbh EA 300/L · Accident: VFR encounter with IMC en route
From Arlington Municipal Airport (AWO) to Ephrata Municipal Airport (EPH)
Event
- NTSB case
- WPR24FA156
- 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
- 1 · all aircraft and ground
- 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
Extra Flugzeugbau Gmbh EA 300/L
- Aircraft type
- Extra EA-300
- 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
- N22MW
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Arlington Municipal Airport (AWO), Arlington, WATo Ephrata Municipal Airport (EPH), Ephrata, WA
- Aircraft age
- About 23 years (built 2001)
- 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
- VFR encounter with IMC
- 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
- Personnel issues › Action/decision
- Personnel issues › Psychological
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The non-instrument-rated pilot departed for the destination airport to attend an aerobatic camp. The airplane followed an interstate through a mountain pass while generally maintaining an altitude of 1,500 ft above ground level (agl). As the airplane continued along the canyon, it began to climb while its airspeed slowed, likely the pilot’s response to entering an area of higher terrain while avoiding clouds. The airplane reached an altitude of about 7,000 ft mean sea level (msl) and an airspeed of 103 kts. The airplane began descending and its speed increased to over 185 kts. The airplane then leveled off briefly before beginning a steeper descent. The airplane then made a 90° left turn and the airspeed decreased while it continued the descent. The airplane impacted terrain in a near-vertical attitude.
Postaccident examination of the wreckage revealed no evidence of a mechanical malfunction or failure. The examination found evidence consistent with the pilot, who was wearing a parachute, having his seatbelt fastened at impact, which indicates he did not attempt to bail out and suggests he did not perceive the airplane to be uncontrollable.
Weather data indicated that, during the last 2 minutes of flight, the airplane was likely operating in instrument meteorological conditions above 3,000 ft msl and encountered icing conditions above 5,400 ft. Forecast information applicable to the accident time included moderate icing above 5,000 ft msl and mountain obscuration due to clouds and mist. There is no record of the pilot obtaining a weather briefing before departure. However, he had commented to the owner of the accident airplane that he might not be able to complete the flight as planned due to weather, indicating an awareness of potential overcast conditions. The pilot had flown through the pass on numerous occasions and likely felt comfortable with the route.
The altitude and airspeed changes during the final 2 minutes of flight are consistent with the pilot attempting to remain clear of clouds while maintaining terrain clearance. After the airplane climbed, it likely encountered icing conditions. Although the reason for the pilot’s left turn could not be determined, the turn occurred while the airplane was in the cloud layer and likely accumulating ice, and it is possible he was attempting to reverse course while descending. The decrease in altitude while approaching the mountain peak, the drastic changes in airspeed, and then the sharp left turn followed by a sudden descent are consistent with the pilot becoming spatially disoriented and entering an aerodynamic stall.
The pilot held the required FAA waiver for the aerobatic camp and was the only person authorized to activate the aerobatic area. This responsibility may have created self-induced pressure to complete the flight despite the adverse weather conditions.
Probable cause
The pilot’s decision to continue flight into icing conditions and inclement weather, which likely led to spatial disorientation when he attempted to divert from the planned course to the destination airport.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR24FA156
- Event ID
- 20240520194296
- Case number
- WPR24FA156
- 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: cc40fad3b8dd2bcb72f1a52281470bec7978ec1606a04718adfdbd395186421c; retrieved 2026-09-15T08:15:01.537Z.