Cessna 177 accident near Columbia, South Carolina, April 1, 2011
On April 1, 2011 at about 10:56 pm local time, a Cessna 177, registered CFFIP, was substantially damaged in an accident during landing (flare/touchdown) near Columbia, South Carolina (Columbia Metropolitan Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper landing flare, which resulted in a hard landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- April 1, 2011 · about 10:56 pm local time
- Place
- Columbia, South Carolina · Columbia Metropolitan Airport · map
- Type
- Accident
- Injuries
- No one was hurt; 2 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 177 · all 177s on the register
- Registration
- CFFIP · no longer on the register · serial 0498
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
According to the pilot, he flew a normal approach, but during the landing flare, the airplane encountered a gust of wind and bounced hard. When it did, he heard a "clunk." The airplane then bounced again before he made a final landing. A postaccident examination of the airplane revealed substantial damage to the fuselage. The pilot reported no pre-existing mechanical anomalies.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Hard landing during landing (flare/touchdown) defining event
The NTSB's findings
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Not attained/maintained
- cause Personnel issues › Action/decision › Action › Incorrect action performance › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Landing flare › Incorrect use/operation
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 298 hours in all; 190 in this make and model; 11 in the last 90 days; 8 in the last 30 days; 198 as pilot in command
- Last flight review: May 21, 2010
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 2,534 hours
- Last inspection: 100-hour inspection, June 10, 2010
- Maximum gross weight: 2,350 lb
- Seats: 3
- Landing gear: fixed
- Engine: Lycoming O-360 (piston); 0 hours total
The flight
- Departed from: CWV Claxton GA at 9:56 pm
- Destination: CAE Columbia SC
- Flight plan: none
- Runway 29, 8,601 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 270° at 17 knots, gusting 20
- Visibility: 10 statute miles
- Sky: scat at 6,500 ft
- Temperature: 61°F (16°C), dew point 34°F (1°C)
- Altimeter: 29.77 inHg
- Observation at 10:56 pm from CAE
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.