FTW83LA229 · Beech B60
Beech B60 · Accident: overrun during landing
From Chickasha Municipal Airport (CHK) to an unrecorded destination
Event
- NTSB case
- FTW83LA229
- 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
Beech B60
- Aircraft type
- Beechcraft 60
- 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
- N2053G
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Chickasha Municipal Airport (CHK), Chickasha, OKTo 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
- Overrun
- 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 › Airspeed, misjudged
- Pilot in command › Brakes(normal), excessive
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
AFTER TOUCHDOWN THE PLT APPLIED BRAKES TO SLOW THE ACFT IN ORDER TO TURN OFF THE MID-FIELD EXIT, BUT THE ACFT WAS GOING TOO FAST FOR THE TURN. THE PLT STATED HE FELT THE BRAKES BEGIN TO BE INEFFECTIVE AT THIS POINT. HE THEN DECIDED TO LET THE ACFT ROLL TO THE END OF THE RWY. THE BRAKES WOULD NOT HOLD WHEN HE APPLIED THEM NEAR THE END. THE PLT THEN ADDED FULL POWER IN ORDER TO PANCAKE THE ACFT INTO THE LAKE OFF THE END OF THE RWY. THE ACFT STRUCK THE WATER 75-100 YDS FROM SHORE. THE BRAKES WERE EXAMINED & THE BRAKE SYSTEM WAS CAPABLE OF OPERATION. HOWEVER, BOTH BRAKE DISKS WERE WORN BEYOND ALLOWABLE LIMITS. THE LEFT DISC MEASURED 0.403 INCH & THE RIGHT DISC MEASURED 0.401 INCH. MINUMUM IS 0.445. IN ADDITION,THE DISCS CONTAINED 'BLUE' SPOTS ON THEIR SURFACE INDICATING THAT THEY HAD BEEN SEVERELY OVERHEATED DURING THE LANDING.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record FTW83LA229
- Event ID
- 20001214X42989
- Case number
- FTW83LA229
- 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: daf3ebb1de1ebab2a8c83f88c89561f665386abc29a051fe0c0f682d6a9b1874; retrieved 2026-09-23T22:17:23.886Z.