ERA14CA367 · Cessna Aircraft Co 162
Atlantic Airways Cessna Aircraft Co 162 · Accident: loss of control in flight during landing
From Leesburg Executive Airport (JYO) to Winchester Regional Airport (OKV)
Event
- NTSB case
- ERA14CA367
- 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
Cessna Aircraft Co 162
- Aircraft type
- Cessna 162
- 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
- N6004U
- Operator
- Atlantic Airways
- Onboard fatalities
- Unknown
- Route
- From Leesburg Executive Airport (JYO), Leesburg, VATo Winchester Regional Airport (OKV), Winchester, VA
- Aircraft age
- About 3 years (built 2011)
- 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 as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported that he was attempting to land the special light-sport-airplane on runway 32, a 5,498-foot-long, 100-foot-wide, asphalt runway. During his first landing attempt, the airplane bounced and he elected to abort the landing. During his second landing attempt, the airplane bounced two times and he again elected to abort the landing; however, the left wing dropped and struck the taxiway. The airplane subsequently came to stop on the ground and sustained substantial damage to the left wing. The student pilot stated that he did not experience any malfunctions with the airplane that would have precluded normal operation. The student pilot had accumulated about 50 hours of total flight experience, all in the same make and model as the accident airplane, and included about 15 hours during the 90 days that preceded the accident. Winds reported at the airport, about the time of the accident, were from 220 degrees at 4 knots.
Probable cause
The student pilot's failure to maintain aircraft control during an aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA14CA367
- Event ID
- 20140731X30452
- Case number
- ERA14CA367
- 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. 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: 853657e9dd9076d3a8027885defbfb045c3d2d03de96618f417425b0f3dc84df; retrieved 2026-09-16T01:02:28.715Z.