# NTSB CHI95LA058: Mooney M20K, N3983H, Minneapolis, MN, December 28, 1994 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: December 28, 1994, 15:17 local (21:17 UTC) - Place: Minneapolis, MN - Coordinates: 44.879371, -93.199073 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=44.8794&lon=-93.1991&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report October 19, 1995 - Report: Approved by Office Director - NTSB case key (mKey): 9813 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI95LA058 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/9813/pdf - Page: https://openairdocs.org/ntsb/CHI95LA058 ## Probable cause the pilot's misjudging of distance and airspeed during the approach to landing which resulted in an overrun. Factors associated with the accident were the separation of the exhaust pipe and the pilot's not understanding communications from the air traffic control tower. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(partial) - mech failure/malf, takeoff - initial climb - exhaust system,manifold/pipe - separation (contributing factor) - precautionary landing - performed, pilot in command - Overrun, landing - roll - communications - not understood, pilot in command (contributing factor) - distance/speed - misjudged, pilot in command (cause) - On ground/water collision with object, landing - roll - object - fence ## Analysis THE PILOT STATED THAT AFTER TAKEOFF AT AN ALTITUDE OF 200 FEET AGL, THE ENGINE BEGAN RUNNING ROUGH AND LOST POWER. HE DECLARED AN EMERGENCY AND WAS INITIALLY CLEARED TO LAND ON RUNWAY 23R FOLLOWED BY A CLEARANCE TO LAND ON ANY RUNWAY. HE STATED HE DID NOT INITIALLY UNDERSTAND THAT HE WAS CLEARED FOR ANY RUNWAY SO HE SET UP TO LAND ON RUNWAY 23R. HE STATED HE WAS TOO CLOSE TO THE RUNWAY BUT HE CONTINUED THE LANDING. THE AIRPLANE TRAVELED OFF THE END OF THE RUNWAY AND CAME TO A STOP AFTER CONTACTING AN AIRPORT PERIMETER FENCE. A POST ACCIDENT TEST RUN OF THE ENGINE REVEALED IT PRODUCED POWER TO 2700 RPM. THE ONLY ANOMALY FOUND WAS A SEPARATION OF THE #6 CYLINDER EXHAUST PIPE NEAR ITS ENGINE MOUNTING FLANGE. ## Factual narrative On December 28, 1994, about 1517 central standard time, a Mooney M20K, N3983H, sustained substantial damage in a precautionary landing at the Crystal Airport, Minneapolis, Minnesota, when it departed the end of runway 23R, and struck the airport perimeter fence. Neither the commercial pilot, nor the single passenger aboard the airplane were injured. The flight had just departed the Crystal Airport with an intended destination of Rockford, Illinois. An IFR flight plan was filed, and visual meteorological conditions prevailed at the time. The pilot stated that at an altitude of approximately 200 feet agl, after takeoff, the engine started running rough and an "significant loss of power" occurred. The pilot declared and emergency and was cleared to land on runway 23R. The pilot was later cleared to land on any runway. The pilot stated he, "Did not fully realize all runway[s] were available." He set up for a landing on runway 23R. He stated he was not set up properly, being too close, but decided to land anyway. The airplane touched down long on the runway, traveled off the end and contacted an airport perimeter fence. A post accident engine test run was conducted. The engine ran up to 2700 rpm without interruption. The only anomaly noted on the was that the #6 cylinder exhaust pipe had separated near the mounting flange. ## Aircraft - Registration: [N3983H](https://openairdocs.org/deregistered/N3983H-2018-09-13), registration cancelled 2018-09-13, S/N 25--0387, built 1980 (OpenAirDocs) - Reported make and model: MOONEY M20K - Registry model: [Mooney M20K](https://openairdocs.org/model/mooney-m20k) (registry code 5870220) (OpenAirDocs) - Registry engine: [Continental TSIO-360 series](https://openairdocs.org/engine/continental-tsio-360-series) (registry code 17019, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 25-0387 - Airframe hours: 1741 - Engines: CONTINENTAL TSIO-360-MB 210 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Werner J. Lindgren - Airworthiness certificate: Standard, Normal - Last inspection: Annual, January 3, 1995, 84 hours before - Departed: MIC - Destination: RFD, ROCKFORD, IL - Flight plan: IFR - Airport: MIC, Crystal, runway 23R, 3,264 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 56; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; flight hours: 2,479 total, 403 in this make and model, 2,400 as pilot in command, 10 in the last 90 days, 6 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 330° at 5 knots - Visibility: 15 statute miles - Lowest ceiling: none - Temperature: 34 °F, dew point 21 °F - Altimeter: 30.00 inHg - Observed at: MIC ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 19941228043019A](https://openairdocs.org/incident/19941228043019A), Dec 28, 1994: Mooney M20K, Minneapolis, MN, Substantial damage. Rough engine on climbout. Overshot runway on return. Ran into a fence. Cause engine problem to be explored. ## Other investigations on N3983H (1) From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. - [NTSB ATL96LA005](https://openairdocs.org/ntsb/ATL96LA005), Oct 13, 1995: Mooney M20K (N3983H), Dalton, GA, substantial damage. Probable cause: Oil starvation for an unknown reason, which resulted in progressive connecting rod failure and subsequent loss of engine power. Factors relating to the accident were: the unfavoable weather and light… From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.