ERA09CA260 · Flight Design Gmbh CTSW
Chesapeake Aviation Services Flight Design Gmbh CTSW · Accident: abnormal runway contact during landing
From Hampton Roads Executive Airport (PVG) to Hampton Roads Executive Airport (PVG)
Event
- NTSB case
- ERA09CA260
- 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
Flight Design Gmbh CTSW
- Aircraft type
- Flight Design CTSW
- 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
- N476CT
- Operator
- Chesapeake Aviation Services
- Onboard fatalities
- Unknown
- Route
- From Hampton Roads Executive Airport (PVG), Chesapeake, VATo Hampton Roads Executive Airport (PVG), Chesapeake, VA
- 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
- 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 student pilot stated that he departed from runway 10 and remained in right closed traffic. He turned on final approach and felt that the airplane was a little high. He considered initiating a go-around, but elected to land further down the runway. As he flared the airplane, he felt an increase in wind. The airplane floated about 5 feet off the ground and the left wing came up as the airplane floated, then touched down on the runway. He considered another go-around, but decided against it because the airplane was too slow, and too far down the runway. The airplane began to porpoise "back up more sharply" touched down on the runway, and bounced into a nose-high attitude. The airplane collided with the runway in a nose-down attitude, collapsed the nose gear, and coming to rest in a nose-down attitude. Examination of the airplane by a Federal Aviation Administration inspector revealed structural damage to the fuselage tunnel. The student pilot stated that he did not experience any mechanical problems with the airplane before the accident.
Probable cause
The student pilot's improper recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA260
- Event ID
- 20090423X55014
- Case number
- ERA09CA260
- 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: 3bc7c59ed40193e504bea6c25aea66c6453da8ca58dd131c0aff70e2c95576df; retrieved 2026-09-15T10:58:40.302Z.