ERA14CA203 · Evolution Aircraft Inc REVO
Evolution Aircraft Inc REVO · Accident: loss of control in flight during landing
From Concord Municipal Airport (CON) to Concord Municipal Airport (CON)
Event
- NTSB case
- ERA14CA203
- 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 REVO
- Aircraft type
- Evolution REVO
- 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
- N2264X
- Operator
- Panuski William R
- Onboard fatalities
- Unknown
- Route
- From Concord Municipal Airport (CON), Concord, NHTo Concord Municipal Airport (CON), Concord, NH
- Aircraft age
- About 1 year (built 2013)
- 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
- 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
- Loss of control in flight
- 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, not marked as estimated; no uncertainty radius is established.
NTSB narrative
According to the student pilot he was returning from a local flight and had entered the pattern with the intent to land. After turning final the pilot noticed he was right of the runway centerline and attempted a left turn to realign the airplane with the runway. During the turn the pilot was forced to correct more due to a slight crosswind. When he finally centered the airplane it was aligned with the left side of the runway, 25 feet over the runway lighting and descending. The pilot then discontinued the landing and initiated a go around maneuver; however, the airplane "dropped 12-15 feet", impacted the ground and the nose gear collapsed before coming to rest on the runway.
Postaccident examination of the airplane by the Federal Aviation Administration revealed substantial damage to both wings. The pilot reported no pre-impact mechanical malfunctions or anomalies that could have precluded normal operation.
Probable cause
The student pilot's failure to maintain control during a go around, which resulted in a collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA203
- Event ID
- 20140420X63845
- Case number
- ERA14CA203
- 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: fb74613ce313745e4f0096ceadd06f3afd44a2fc45ef1bd1979bbac1851c255d; retrieved 2026-09-15T23:31:45.968Z.