MKC83FA225 · Beech 60
Beech 60 · Accident: total loss of engine power (mechanical failure) en route
From an unrecorded airport to Gerald R. Ford International Airport (GRR)
Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- MKC83FA225
- 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 60 Possible conflict
- 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
- N7277R
- Operator
- Paul E. Geddes & Scott Brunke
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Gerald R. Ford International Airport (GRR), Grand Rapids, MI
- 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
- En route · climb to cruise
- 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
- Total loss of engine power (mechanical failure)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Engine assembly, valve, intake › Fatigue
- Engine assembly, valve, intake › Other
- Pilot in command › Airspeed(vmc), not maintained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
SHORTLY AFTER TAKEOFF, THE LEFT ENG BEGAN TO PROGRESSIVELY LOSE POWER & WAS SHUT DOWN. THE AIRCREW NOTIFIED BEECH TOWER OF THE PROBLEM & REPORTED THEY WOULD LIKE TO RETURN & LAND. THE ACFT WAS OBSERVED ON FINAL APCH TO RWY 18 WITH THE GEAR EXTENDED & THE LEFT PROP STOPPED. BEFORE LANDING, THE ACFT BEGAN VEERING TO THE LEFT. IT CROSSED OVER THE END OF THE ARPT AT ABOUT 40 FT AGL & 300 FT LEFT (EAST) OF THE RWY. THE LEFT WING & NOSE DROPPED & THE ACFT IMPACTED THE RAMP, LEFT WING 1ST. THE ACFT THEN SKIDDED ACROSS THE RAMP ON A HEADING OF 160 DEG & COLLIDED WITH & DAMAGED 3 OTHER ACFT; A BEECH F33A, N1833S; ANOTHER BEECH 60, N6747D; & A BEECH 58, N5800B. AN INVESTIGATION REVEALED THAT THE #2 EXHAUST VALVE LIFTER HAD BECOME FLAT & THE #2 EXHAUST VALVE HAD FAILED FROM FATIGUE.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record MKC83FA225
- Event ID
- 20001214X44641
- Case number
- MKC83FA225
- 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: c97b38e05141697c95ddafa7258292954331e87d2284113e4db6e7b4e02155af; retrieved 2026-09-23T21:18:12.277Z.