GAA16CA098 · Johnson Glenn L ZODIAC 601 XL B
Johnson Glenn L ZODIAC 601 XL B · Accident: abnormal runway contact during landing
From Chesapeake Regional Airport (CPK) to Chesapeake Regional Airport (CPK)
Event
- NTSB case
- GAA16CA098
- 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
Johnson Glenn L ZODIAC 601 XL B
- Aircraft type
- Johnson Glenn ZODIAC 601
- 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
- N676L
- Operator
- Johnson Glenn L
- Onboard fatalities
- Unknown
- Route
- From Chesapeake Regional Airport (CPK), Chesapeake, VATo Chesapeake Regional Airport (CPK), Chesapeake, VA
- Aircraft age
- About 7 years (built 2009)
- 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 · landing roll
- 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 › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot of the tricycle landing gear equipped airplane, he was performing a normal approach and landing to an asphalt runway. He reported that after accomplishing the landing flare he recalled "jockeying" the stick in order to get closer to the runway. The airplane touched down, bounced three times and the pilot added power. The airplane struck the ground a fourth time and the nose gear collapsed. The pilot reported that the airplane skidded down the center of the runway and came to a halt. The airplane sustained substantial damage to the firewall and frame.
The pilot reported that there were no mechanical failures or anomalies prior to or during the flight that would have prevented normal flight operation.
Probable cause
The pilot's failure to maintain pitch control during the landing, causing the airplane to bounce and the nose gear to collapse, resulting in substantial damage to the firewall and frame.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA098
- Event ID
- 20160111X90408
- Case number
- GAA16CA098
- 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: ebb214167aa651f500769fbbf530077cb0990468d7a75320a1c47dec9c0dddde; retrieved 2026-09-16T03:05:03.063Z.