ERA20CA242 · Cessna 177 Undesignat
Cessna 177 Undesignat · Accident: hard landing
From Bradford County Airport (N27) to an unrecorded destination
Event
- NTSB case
- ERA20CA242
- 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
Cessna 177 Undesignat
- Aircraft type
- Cessna 177
- 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
- N29334
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bradford County Airport (N27), Towanda, PATo not recorded
- Aircraft age
- About 52 years (built 1968)
- 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
- Hard landing
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
As the pilot approached the destination airport he noted a thunderstorm cell in the vicinity as he entered the airport traffic pattern. During the subsequent landing the airplane, “…hit and porpoised twice.” The pilot further described that as the landing continued, he was losing control, and the airplane was drifting to the left side of the runway, so he initiated a go around and joined the traffic pattern for another landing. The second landing was normal, and he taxied to the ramp. Postaccident examination of the airplane revealed that the fuselage structure was substantially damaged during the first landing. Review of the weather conditions that prevailed at the time of the accident indicated that the pilot landed with right quartering crosswind. The pilot reported that there were no mechanical malfunctions or failures of the airplane that would have precluded normal operation. The pilot further stated that he should have been less rushed to land and should have extended the downwind for landing as he did after the go around, to a safe, less rushed landing and tie down.
Probable cause
The pilot’s improper landing flare, which resulted in a hard, bounced landing, and substantial damage to the airplane’s fuselage.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20CA242
- Event ID
- 20200701X12327
- Case number
- ERA20CA242
- 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: e1ff0723eab1225ad3a393576ebef8ec60cf39bec17b6309cdcb338982736bc5; retrieved 2026-09-16T11:58:49.545Z.