# Accident 20030523010469A: Mooney M20K, Colorado Spring, CO, May 23, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 23, 2003, 21:53 local time
- Place: Colorado Spring, CO
- Airport: City Of Colorado Springs Municipal
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.8008° N, 104.7000° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.8008&lon=-104.7000&mi=10
- Aircraft: N231JM, a cancelled registration (https://openairdocs.org/deregistered/N231JM-2013-10-23) (OpenAirDocs)
- Registry model: Mooney M20K (registry code 5870220, https://openairdocs.org/model/mooney-m20k) (OpenAirDocs)
- Registry engine: Continental TSIO-360 series (registry code 17019, https://openairdocs.org/engine/continental-tsio-360-series) (OpenAirDocs)
- Reported make and model: MOONEY M20K
- Reported engine: CONT TSIO360*
- Fatal injuries: 0
- Pilot flight hours: 41 in this make and model, 272 in the last 90 days
- NTSB investigation: [NTSB DEN03LA086](https://openairdocs.org/ntsb/DEN03LA086) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030523010469A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AIRCRAFT ATTEMPTED TO LAND ON RUNWAY 35R AT COS. PILOT EXPLAINED THAT AFTER CROSSING THRESHOLD ON SPEED AND ON CENTERLINE, AIRCRAFT BEGAN A FLARE; ALL APPEARED NORMAL. THE AIRCRAFT THEN WAS FORCED TO THE LEFT EDGE OF THE RUNWAY AS THE RIGHT WING RAISED UP, ACCORDING TO THE PILOT. PILOT SAID THAT SOMETHING UNKNOWN THEN "CLIPPED" THE AIRCRAFT CAUSING IT TO BE POINTED TO THE NORTHWEST. PILOT SPECULATED THAT THE "CLIP" WAS THE IMPACT OF THE LEFT MAIN GEAR OFF THE EDGE OF THE RUNWAY, BUT THE EXACT CAUSE REMAINS UNDETERMINED. HE SAID HE ATTEMPTED A GO-AROUND BUT NOTICED A POSSIBLE "DELAY" IN ENGINE RESPONSE. THE AIRCRAFT DID NOT GO AROUND, AND HIT A STOP SIGN ON A SERVICE ROAD RUNNING BETWEEN RUNWAY 35R AND TAXIWAY ECHO. THE PILOT SHUT DOWN THE ENGINE AS THE AIRCRAFT CONTINUED DIAGONALLY ACROSS TAXIWAY ECHO AND THEN ACROSS THE UNIMPROVED AIRPORT PROPERTY FOR APPROXIMATELY .34 MILES. THE AIRCRAFT THEN HIT A CHAIN-LINK FENCE, PROCEEDED THROUGH IT, AND CAME TO REST APPROXIMATELY 100 FEET BEYOND THE FENCE. WIND WAS REPORTED BY THE AIR TRAFFIC CONTROLLER AS 100 DEGREES AT 15 WHEN THE AIRCRAFT WAS CLEARED TO LAND, ACCORDING TO PERSONNEL AT THE COS ATCT.

## The NTSB's investigation of this event (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 DEN03LA086](https://openairdocs.org/ntsb/DEN03LA086), May 24, 2003: Mooney M20K (N231JM), Colorado Sprngs, CO, substantial damage. Probable cause: the pilot's improper decision to land in the reported crosswind conditions, and his failure to maintain aircraft control. Contributing factors were the crosswind, rough terrain, airport stop sign,…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
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.