CEN15LA219
2015-04-14 · Evart, Michigan, United States · None · 1 aircraft · Status: Completed
Airport 9C8
Current FAA registration · N850WM
- Make / Model
- SOCATA TBM 700
- Year of manufacture
- 2006 · 9 years old at event
- Engine
- P&W CANADA PT6A-66 (850 hp)
- Seats / Engines
- 7 seats · 1 engine
- Last airworthiness date
- 20060414
- ADS-B equipped
- Yes — Mode-S ABA958
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's failure to follow the Before Landing checklist and to extend the landing gear and the flight instructor’s inadequate supervision, which resulted in a gear-up landing.
Factual narrative
On April 14, 2015, about 1145 eastern daylight time, a Socata TBM 700, N850WM, experienced a gear-up landing on runway 24 (3,804 feet by 75 feet, asphalt) at Evart Municipal Airport (9C8), Evart, Michigan. The airplane sustained substantial damage to the bottom fuselage skin. The commercial pilot and flight instructor were uninjured. The airplane was registered to Wings Up III LLC and operated by the pilot. The instructional flight was operated under Code of Federal Regulations Part 91 as an instructional flight, which was not operating on a flight plan. Visual meteorological conditions prevailed at the time of the accident. The local flight last departed from 9C8 about 1100 and was planned to return to 9C8 but diverted to Roben-Hood Airport (RQB), Big Rapids, Michigan. The airplane accident was not reported by the owner/operator but was discovered by a Federal Aviation Administration (FAA) inspector from the Grand Rapids Flight Standards District Office after being notified of the accident by a person on April 28, 2015. The airplane had been moved to Socata North America, Inc., Pompano, Florida where it was going to undergo repair as instructed by the insurance representatives for Traverse City Helicopters, LLC. On May 6, 2015, the Federal Aviation Administration reported the accident to the National Transportation Safety Board Central Region Duty Officer. The flight instructor stated that they departed from 9C8 with a normal take-off from runway 24 followed by "basic" visual flight rules air work that included steep turns and slow flight. They returned to 9C8 for pattern work where a normal landing was performed followed by a landing using 10 degrees of flaps and a landing with 0 degrees of flaps. While performing the approach/landing with 0 degrees of flaps, the landing gear was not extended at midfield, as had happened on the previous two landings. As the airplane descended into ground effect, the pilot and the flight instructor realized that the landing gear was not down and "took immediate steps to go around." The rear ventral strikes and a portion of the aft belly contacted the runway before descent could be reversed, and the propeller struck the runway. They continued the climb out, assessed the damage and controllability, and then diverted to RQB where a maintenance facility could look at the airplane. The flight landed at RQB without further incident. During a telephone conversation with the pilot, the pilot said he was a "long time fixed wing pilot." He said that the instructional flight was part of an airplane checkout required by the insurance company, and the flight instructor was recommended by the insurance company. The pilot stated that he went through "a lot of ground stuff" as part of his training in the accident airplane, and the accident flight was the first flight flown with the flight instructor. The pilot stated that prior to the accident he did not know that there was no gear warning annunciation without the flaps extended. The pilot said that he was the flying pilot at the time of the accident, and the flight instructor was demonstrating a no flap approach. The pilot said they prior they were flying a "quite large" traffic pattern. The pilot said that he was "distracted" from watching the airspeed and attitude of the airplane and during touchdown he heard the noise of the airplane contact with the runway and applied power to initiate an aborted landing because "there was not much runway left." Once airborne, they got the airplane stable and decided to continue the flight to an airport that had more aircraft services available. According to the TBM 700 Pilot Operating Handbook, Section 4, Normal Procedures, Before Landing checklist, the landing gear control was to be in the down position, the three landing gear green lights were to be on, and the red warning light was to be off. A review of the pilot's logbook showed that he did not have a high altitude endorsement under Part 61.31(g) "Additional training required for operating pressurized aircraft capable of operating at high altitudes." The pilot's logbook showed that he accumulated a total of 19.7 hours of dual instruction received in the Socata TBM 700, and accumulated no pilot-in-command flight time in the Socata TBM 700. The flight instructor and commercial pilot were conducting a local instructional flight as part of an insurance requirement. The flight instructor stated that, after performing pattern work, the pilot performed two landings and that, while performing the approach for a third landing with 0 degree of flaps, the landing gear were not extended at midfield. He stated that this had also happened on the previous two landings. He added that, as the airplane descended into ground effect, he and the pilot realized that the landing gear were not down and "took immediate steps to go around"; however, the airplane contacted the runway surface with the gear up. The pilot stated that he was "distracted" by watching the airplane's airspeed and attitude and that, during touchdown, he heard the airplane contact the runway and that he then applied power to initiate an aborted landing because "there was not much runway left." Given that the flight instructor had noted that the pilot had not extended the landing gear by midfield on the previous two landings, he should have had a heightened focus on the gear's position during the subsequent/accident landing. Further, the Before Landing checklist stated to extend the landing gear and verify that the landing gear position indicator lights were green. If the pilot had followed the Before Landing checklist or if the flight instructor had been adequately supervising the pilot, the landing gear likely would have been extended upon landing. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
FAA avdata. C = Cause, F = Factor.
- C Personnel issues-Task performance-Use of equip/info-Use of checklist-Student/instructed pilot - C
- C Personnel issues-Task performance-Use of equip/info-Use of equip/system-Student/instructed pilot - C
- C Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Configuration-Not attained/maintained - C
- C Aircraft-Aircraft systems-Landing gear system-Gear extension and retract sys-Not used/operated - C
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other person-Instructor/check pilot - C
Verbatim from NTSB's published report. Source file
NTSB_2015_CEN15LA219.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (maintenance). All research papers
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA) From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2026 · Article (Reliability Engineering & System Safety) Understanding human error in military aviation maintenance: The role of Performance shaping factors, cognitive workload and error orientation
- Semantic Scholar 2025 · Article (Applied Sciences) Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Semantic Scholar 2024 · Article (Defence Science Journal) Modelling of Human Factors in Aviation Maintenance Using HFACS ME Human Factors Analysis and Classification System Maintenance Extension and Bayesian Network
Aircraft maintenance is a complex task involving a skilled human workforce, spare parts, and various other resources. Human factors are an inherent element of the human workforce.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER) A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER) Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…