ATL89LA011 · Cessna 177B
Boyertown Flying Club Cessna 177B · Accident: hard landing
From I07 · Summersville, WV to an unrecorded destination
Event
- NTSB case
- ATL89LA011
- 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
- 0
- 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 177B
- 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
- N17223
- Operator
- Boyertown Flying Club
- Onboard fatalities
- Unknown
- Route
- From I07 · Summersville, WVTo not recorded
- 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
- First occurrenceThe 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
- Pilot in command › Altitude, misjudged
- Pilot in command › Flare, premature
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT REPORTED THAT HE INITIALLY FLARED TOO HIGH DURING THE LANDING. HE RECOVERED AND THE ACFT SUBSEQUENTLY TOUCHED DOWN 'FIRMLY' ON THE MAIN GEAR. THE ACFT THEN BEGAN TO VEER TO THE RT 'AS IF THE RT BRAKE WAS LOCKED'. THE PLT ATTEMPTED TO ABORT THE LDG & THE ACFT PANCAKED INTO A DUNE ADJACENT TO THE RWY. A MECHANIC WHO EXAMINED THE AIRPLANE AFTERWARD REPORTED THAT THE PLT STATED TO HIM THAT THE AIRPLANE HAD LANDED HARD. THE MECH REPORTED FINDING THAT THE RT WHEEL AXLE WAS BENT WHICH HAD RESULTED IN THE FWD SIDE OF THE TIRE BEING DISPLACED OTBD. NO EVIDENCE OF BRAKE MALFUNCTION WAS FOUND. ACCORDING TO THE ARPT FACILITY DIRECTORY, THE ARPT HAD NO RWY LIGHTS AND CLOSED 30 MINUTES AFTER SUNSET. LOCAL SUNSET OCCURRED AT 1835, ACCORDING TO THE NWS. THE PLT REPORTED THE TIME OF THE ACCIDENT AT 1930. A SHERIFF'S DEPUTY WHO INVESTIGATED THE ACCIDENT REPORTED THAT IT OCCURRED AT ABOUT 1955.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record ATL89LA011
- Event ID
- 20001213X26984
- Case number
- ATL89LA011
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 975f688a7ada66b1f5ce692d9513ce3697f500a036dbfc51e4267a691ea5bf57; retrieved 2026-09-22T00:22:14.270Z.