ERA24LA223 · Beechcraft TC-12B
Lee County Mosquito Control District Beechcraft TC-12B · Accident: loss of control on ground during landing
From Punta Gorda Airport (PGD) to an unrecorded destination
Event
- NTSB case
- ERA24LA223
- 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
- Event fatalities
- Unknown
- 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
- Government
- 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
Beechcraft TC-12B
- Aircraft type
- Beechcraft TC-12
- 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
- N762MC
- Onboard fatalities
- Unknown
- Route
- From Punta Gorda Airport (PGD), Punta Gorda, FLTo not recorded
- Aircraft age
- About 44 years (built 1980)
- 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
- Public Aircraft
- 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
- 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
- Loss of control on ground
- 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
- Aircraft › Aircraft propeller/rotor
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
At the conclusion of a training flight that included two uneventful landings using ground fine/beta or reverse thrust settings, the pilots of the multi-engine, turbo-propeller equipped airplane returned to the home base airport. The pilot flying (PF) reported that he moved each propeller control full forward. He reported that the airplane crossed the runway threshold at 110 knots indicated airspeed (KIAS), or landing reference speed (Vref) plus 22 knots (kts). The airplane touched down with both power levers at flight idle and the “REV NOT READY” annunciator extinguished. After touchdown, the PF moved both power levers aft of the idle gate into beta, then into reverse. Recorded GPS data revealed that the airplane began deviating slightly to the left while decelerating, then about 8 seconds after touchdown, while at 66 kts groundspeed (about 72 KIAS), the airplane quickly veered to the left. The flight crew applied right rudder and right brake, but were unable to correct the airplane’s trajectory. The pilot monitoring (PM) stated that it felt like the airplane was accelerating as it departed the left side of the runway. The GPS data showed that the airplane continued to slow while rolling off the runway. The airplane continued through a 5-ft-deep depression in the grass off the side of the runway before it came to rest with the left main and nose landing gear collapsed, resulting in substantial damage to the fuselage and left wing.
Flight control continuity was confirmed from the cockpit to each control surface, while the rudder and aileron trims were neutral. No discrepancies were noted with either engine power lever or propeller control lever. There was no evidence of pre-impact mechanical failures or malfunctions that would have precluded normal operation of either propeller constant speed unit (CSU) or its attached beta valve; either propeller; or either fuel control unit. No propeller-related issues were reported by the accident flight crew during the two previous landings earlier that day using beta or reverse, nor were any propeller discrepancies reported by other pilots who had recently flown the airplane and employed beta or reverse.
Flight testing of an exemplar airplane equipped with the same engines and propellers revealed that, with each power lever at flight idle and each propeller control full forward, the propeller CSUs were still governing to 120 KIAS, while flight testing with the propeller controls set to 1,700 rpm revealed that the propeller CSUs were still governing to 90 KIAS; safety concerns prevented flight testing below that airspeed. By design, propeller blade movement into beta and reverse cannot occur unless its respective propeller CSU is in an underspeed condition.
Based on the examination of the airplane, there was no evidence of any mechanical anomaly with either propeller CSU or its beta valve that would have prevented the propellers from entering beta and then reverse as commanded if either CSU had been in an underspeed condition. Flight testing confirmed that if the propeller controls were full forward, any airspeed below 120 KIAS would have resulted in both propeller CSUs being in an underspeed condition; the airplane was well below that speed at touchdown.
When the PF moved each power lever aft of the flight idle gate and into beta, then reverse, after touchdown, the propellers should have produced symmetrical reverse thrust. However, the circumstances of the accident flight are consistent with production of asymmetric reverse thrust, which resulted in the flight crew’s inability to maintain directional control and a runway excursion. Based on the postaccident examination of the airplane and propeller systems, the reason for the asymmetric reverse thrust could not be determined.
Probable cause
The asymmetric reverse thrust during the landing roll for reasons that could not be determined, resulting in the flightcrew’s inability to maintain directional control and a subsequent runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA223
- Event ID
- 20240520194291
- Case number
- ERA24LA223
- 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, cause areas. 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: e739b46185c6b26f503d4d34fdd41cfaba7ceb61fc1b7eb472271fc5d078e236; retrieved 2026-09-16T18:47:10.637Z.