ATL95LA011 · Cessna 185
Cessna 185 · Accident: airframe, component or system failure during landing
From 0A9 to an unrecorded destination
Event
- NTSB case
- ATL95LA011
- 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 185
- Aircraft type
- Cessna 185
- 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
- N6688H
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 0A9To 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 · landing roll
- 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
- Airframe, component or system failure
- 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
DURING A THREE POINT LANDING DEMONSTRATION, THE LEFT PEDAL ON THE CO-PILOT'S SIDE OF THE COCKPIT COLLAPSED, AND THE INSTRUCTOR PILOT LOST CONTROL OF THE AIRPLANE. EXAMINATION OF THE RUDDER PEDAL ASSEMBLY FAILED TO DISCLOSE A COMPONENT FAILURE. ACCORDING TO THE MAINTENANCE INSPECTOR, THE LOCKING ASSEMBLY WAS RE-ENGAGED AND THE RUDDER ASSEMBLY OPERATED NORMALLY. THE INSPECTOR CONCLUDED THAT, HEAVY BRAKING CAUSED THE LOCKING ASSEMBLY TO FLEX ENOUGH TO RELEASE. THE MAINTENANCE INSPECTOR ALSO STATED THAT THERE HAD BEEN A FEW MALFUNCTIONS OF THE LOCKING ASSEMBLY. THOSE INCIDENTS REPORTED BY MISSIONARY PILOTS WERE CORRECTED BY DISABLING THE STOW ASSEMBLY, AND LOCKING THE PEDALS IN THE UPRIGHT POSITION.
Probable cause
THE FLEXING OF THE RUDDER PEDAL CONTROL LOCKING ASSEMBLY WHICH RESULTED IN THE COLLAPSE OF THE CO-PILOT'S LEFT PEDAL DURING HEAVY BRAKING.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ATL95LA011
- Event ID
- 20001206X02548
- Case number
- ATL95LA011
- 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: 066dff91e982a56946b7579f9a9882c050936459e465239d54c697b2b1436db4; retrieved 2026-09-23T00:28:33.258Z.