WPR23LA277 · Evolution Aircraft Inc REVOLT
Evolution Aircraft Inc REVOLT · Accident: aircraft wake turbulence encounter during landing
From Casper, WY to Casper-Natrona County International Airport (CPR)
Event
- NTSB case
- WPR23LA277
- 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
- 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
Evolution Aircraft Inc REVOLT
- Aircraft type
- Evolution REVOLT
- Category
- Weight-Shift
- 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
- N277GH
- Operator
- KC Construction
- Onboard fatalities
- Unknown
- Route
- From Casper, WYTo Casper-Natrona County International Airport (CPR), Casper, WY
- Aircraft age
- Not recorded
- 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
- Landing · flare/touchdown
- 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
- Aircraft wake turbulence encounter
- 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 oper/perf/capability
- Personnel issues › Task performance
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 reported being cleared to land by air traffic control and reported being cautioned of wake turbulence by an airplane that landed ahead in sequence. The pilot aimed to touchdown at a point beyond the presence of the wake turbulence. The airplane encountered light turbulence prior to landing and contacted the runway misaligned with the runway centerline. The pilot applied opposite input correction which produced a roll force resulting in the right wing contacting the ground, substantially damaging the airplane. The pilot reported that there were no preaccident mechanical failures or malfunctions with the airplane that would have precluded normal operation.
Probable cause
The pilot’s loss of directional control during landing after encountering wake turbulence.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR23LA277
- Event ID
- 20230719192666
- Case number
- WPR23LA277
- 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: 74bde598f74bd75d2c8dc30712f649f5f826b6542268cb39cd286c477fb152f8; retrieved 2026-09-16T17:52:59.194Z.