20030523010469A

Accident · Substantial damage

FAA accident report · Mooney M20K · Colorado Spring, CO · May 23, 2003

Date
May 23, 2003 · 21:53 local
Place
Colorado Spring, CO
Airport
City Of Colorado Springs Municipal
Phase of flight
Level Off Touchdown
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N231JM
NTSB investigation
NTSBDEN03LA086
Reported as
Mooney M20K
Reported engine
Continental TSIO360*
Fatal injuries
0
Pilot’s flight hours
41 in this make and model272 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry 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.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

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

As the FAA filed it

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

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.