# NTSB ERA09CA260: Flight Design Ctsw, N476CT, Chesapeake, VA, April 21, 2009

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: April 21, 2009, 12:35 local (16:35 UTC)
- Place: Chesapeake, VA
- Coordinates: 36.779998, -76.448608 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=36.7800&lon=-76.4486&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Defining event: [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090)
- Highest injury: No injuries
- Injuries: 1 uninjured
- Status: Completed, report June 11, 2009
- Report: Approved by Office Director
- NTSB office: Eastern Region Aviation
- Parties: FAA Richmond FSDO
- NTSB case key (mKey): 73717
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA09CA260
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/73717/pdf
- Page: https://openairdocs.org/ntsb/ERA09CA260

## Probable cause

The student pilot's improper recovery from a bounced landing.

## Findings

NTSB's coded findings; those marked are part of the probable cause.

- [Action: incorrect action performance](https://openairdocs.org/ntsb-findings/02041015): Personnel issues › Action/decision · Student/instructed pilot (probable cause); cases with it: [Flight Design CTSW, 5 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md?model=0600001), [All aircraft, 1,386 cases](https://openairdocs.org/ntsb-findings/02041015/cases.md)
- [Performance/control parameters: landing flare](https://openairdocs.org/ntsb-findings/01062041): Aircraft › Aircraft oper/perf/capability · Incorrect use/operation (probable cause); cases with it: [Flight Design CTSW, 5 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md?model=0600001), [All aircraft, 1,285 cases](https://openairdocs.org/ntsb-findings/01062041/cases.md)

## Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event best describes what happened.

- [Landing-flare/touchdown: Abnormal runway contact](https://openairdocs.org/ntsb-events/090) (defining event); cases with it: [Flight Design CTSW, 4 cases](https://openairdocs.org/ntsb-events/090/sequence.md?model=0600001), [All aircraft, 1,506 cases](https://openairdocs.org/ntsb-events/090/sequence.md)
- [Landing-landing roll: Landing gear collapse](https://openairdocs.org/ntsb-events/094); cases with it: [Flight Design CTSW, 6 cases](https://openairdocs.org/ntsb-events/094/sequence.md?model=0600001), [All aircraft, 1,787 cases](https://openairdocs.org/ntsb-events/094/sequence.md)

## Analysis

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.

## Factual narrative

The student pilot stated he departed from runway 10 and remained in right closed traffic. He turned on final approach, and felt 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, the left wing came up as the airplane floated, and touched down on the runway. He considered another go-around, but decided against it because the airplane was to slow, and to 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 came 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 he did not experience any mechanical problems with the airplane before the accident.

## Aircraft

- Registration: [N476CT](https://openairdocs.org/deregistered/N476CT-2018-05-30), registration cancelled 2018-05-30, S/N 07-07-03, built 2007 (OpenAirDocs)
- Reported make and model: FLIGHT DESIGN GMBH CTSW
- Registry model: [Flight Design CTSW](https://openairdocs.org/model/flight-design-ctsw) (registry code 0600001) (OpenAirDocs)
- Registry engine: [Rotax 912ULS series](https://openairdocs.org/engine/rotax-912uls-series) (registry code 55572, 4 cycle) (OpenAirDocs)
- Category: Airplane
- Serial number: 07-07-03
- Airframe hours: 144
- Engines: ROTAX 912ULS 100 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Operator: Chesapeake Aviation Services
- Registered owner: Jam Air LLC
- Airworthiness certificate: Special, Experimental light sport (Special)
- Last inspection: 100 hour, February 20, 2009, 20 hours before
- Departed: PVG, Chesapeake, VA
- Destination: PVG, Chesapeake, VA
- Flight plan: Unknown
- Airport: PVG, Hampton Roads Exec Airport, runway 10, 4,056 × 70 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Student pilot; age 49; injuries: none; student; seat: left; flight hours: 32 total, 32 in this make and model, 1 as pilot in command, 30 in the last 90 days, 14 in the last 30 days

## Weather

- Conditions: Visual (VMC), Day
- Wind: 220° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 81 °F, dew point 55 °F
- Altimeter: 30.00 inHg
- Observed at: SFQ, 10 nm away

## Other investigations on N476CT (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ERA14CA298](https://openairdocs.org/ntsb/ERA14CA298), Jun 14, 2014: Flight Design Ctsw (N476CT), Milton, FL, substantial damage. Probable cause: The pilot's failure to maintain the proper approach path, and his delayed remedial action, which resulted in a runway undershoot and collision with terrain prior to the runway.

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
