CEN17LA323 · North American SNJ-4
North American SNJ-4 · Accident: abnormal runway contact during landing
From Akron Fulton International Airport (AKR) to Ashland County Airport (3G4)
Event
- NTSB case
- CEN17LA323
- 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
North American SNJ-4
- Aircraft type
- North American SNJ-4
- 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
- N243CC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Akron Fulton International Airport (AKR), Akron, OHTo Ashland County Airport (3G4), Ashland, OH
- Aircraft age
- About 74 years (built 1943)
- 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
- Abnormal runway contact
- 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 › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The private pilot of the tailwheel-equipped airplane stated that, during a "wheel landing," the airplane bounced twice upon touchdown then veered off the runway into a grass area. The pilot was unable to return the airplane to the runway surface because the airplane was "slipping on the grass" while the pilot applied left rudder and left wheel brake. The airplane nosed over when it came to a stop in the grass area and came to rest inverted. The pilot stated that there were no mechanical malfunctions or failures with the airplane. According to the Airplane Flying Handbook, corrective action from a bounced landing is dependent upon its severity, and such action can range from an application of power to cushion a subsequent landing to performance of a go-around.
Probable cause
The pilot’s improper recovery from a bounced landing, which resulted in a loss of directional control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN17LA323
- Event ID
- 20170821X41707
- Case number
- CEN17LA323
- 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: c4305ab10131a1a03a0c21dbf1ad9500268a5c1a9ba86db1c6fe2240c3b9e0ab; retrieved 2026-09-16T05:43:55.604Z.