37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 139825 |
Time | |
Date | 199003 |
Day | Fri |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : csq |
State Reference | IA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
Flight Phase | landing other |
Flight Plan | VFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : commercial pilot : instrument |
Experience | flight time last 90 days : 70 flight time total : 5170 flight time type : 440 |
ASRS Report | 139825 |
Events | |
Anomaly | other anomaly other anomaly other other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : unable |
Consequence | faa : investigated other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
On a VFR flight plan from manhattan municipal (ks) to csq in an small aircraft (tail dragger), I obtained a WX brief and NOTAM check with wichita FSS, as well as filing (on the ground). I talked to columbia flight watch en route for a WX update and to give a PIREP. Winds were reported to be around 170-190 degrees on the ground in the des moines vicinity. I approached the field at csq from the south and noted the asphalt runway 16/34 and the turf runway 22/04 as depicted in my flight guide manual and AOPA airport directory. I tried to call csq unicom on 122.8 several times with no success, as well as ft dodge radio on 122.65 and 122.3, 'no joy.' I set up a standard approach to runway 15 and noticed the wind was variable. On final, I ran out of rudder and noticed the wind was directly crosswind (left). I waved off and set up an approach to the turf runway 04, which looked dry. On final it was apparent I would land a little long and had 1/2 flaps set for a go around if need be. I touched down in a 3 point landing, but was not slowing as fast as I anticipated. Applying brakes, the aircraft began decelerating faster; however, the end of the runway sloped downward and the turf suddenly turned to mud. The brakes locked as the aircraft continued toward a wire fence at the end. The aircraft impacted the fence at about 10 mph, at which time a fence wire broke the wind screen, as the engine (at idle) quit. The aircraft came to a halt. I checked both passenger and they had no injuries. I secured the engine and equipment and got out ot survey the damage. The left lift strut was bent on the forward portion from apparently hitting a metal post. The wind screen struts over the glare shield panel were bent and 1 side of the propeller was bent (twisted). All other areas were untouched; i.e., wings, landing gear, fuselage and empennage were undamaged. After surveying the aircraft and checking to make sure the passenger were still ok, I went to the FBO's office to get help. The WX looked like it might produce a rain shower at any time that could possibly damage radio equipment or make the task of pulling the aircraft out extremely difficult. The FBO was not at the office, so I closed out my flight plan with ft dodge FSS and found a man working on an aircraft in 1 of the hangars. We examined this position of the aircraft in relation to the fence and hill, then he went to get a tractor and rope. I unloaded the baggage and went back to the FBO's office where the passenger had gone. When I got to the FBO's office, the FBO had returned. He mentioned that he had notified the state that the runway that I had used was closed (not according to my flight guide or NOTAM brief). We obtained a small (1500 pounds) tractor and pulled the aircraft away from the fence west/O further damage. We placed the aircraft in a vacant hangar to protect it from the elements. We (myself and passenger) obtained transportation back to ames, ia. I tried to call FAA via the 1-800 # early the next morning. I was able to make contact by late morning via FSS. I gave my report, the name of the mechanic I would dispatch to repair the aircraft, the csq FBO and the pertinent details. I also notified my insurance agent and my employer. I believe the variable winds and muddy field (they had received 5' of rain) were the primary causes of the overrun. A frontal passage was experienced which made the runway to be used questionable. Being able to talk to someone on a unicom would have been extremely helpful.
Original NASA ASRS Text
Title: GA SMA PLT ENCOUNTERS MUD WHILE LNDG ON TURF STRIP AT CSQ, OVERRUNS RWY AND HITS FENCE WITH SUBSEQUENT DAMAGE.
Narrative: ON A VFR FLT PLAN FROM MANHATTAN MUNI (KS) TO CSQ IN AN SMA (TAIL DRAGGER), I OBTAINED A WX BRIEF AND NOTAM CHK WITH WICHITA FSS, AS WELL AS FILING (ON THE GND). I TALKED TO COLUMBIA FLT WATCH ENRTE FOR A WX UPDATE AND TO GIVE A PIREP. WINDS WERE RPTED TO BE AROUND 170-190 DEGS ON THE GND IN THE DES MOINES VICINITY. I APCHED THE FIELD AT CSQ FROM THE S AND NOTED THE ASPHALT RWY 16/34 AND THE TURF RWY 22/04 AS DEPICTED IN MY FLT GUIDE MANUAL AND AOPA ARPT DIRECTORY. I TRIED TO CALL CSQ UNICOM ON 122.8 SEVERAL TIMES WITH NO SUCCESS, AS WELL AS FT DODGE RADIO ON 122.65 AND 122.3, 'NO JOY.' I SET UP A STANDARD APCH TO RWY 15 AND NOTICED THE WIND WAS VARIABLE. ON FINAL, I RAN OUT OF RUDDER AND NOTICED THE WIND WAS DIRECTLY XWIND (LEFT). I WAVED OFF AND SET UP AN APCH TO THE TURF RWY 04, WHICH LOOKED DRY. ON FINAL IT WAS APPARENT I WOULD LAND A LITTLE LONG AND HAD 1/2 FLAPS SET FOR A GAR IF NEED BE. I TOUCHED DOWN IN A 3 POINT LNDG, BUT WAS NOT SLOWING AS FAST AS I ANTICIPATED. APPLYING BRAKES, THE ACFT BEGAN DECELERATING FASTER; HOWEVER, THE END OF THE RWY SLOPED DOWNWARD AND THE TURF SUDDENLY TURNED TO MUD. THE BRAKES LOCKED AS THE ACFT CONTINUED TOWARD A WIRE FENCE AT THE END. THE ACFT IMPACTED THE FENCE AT ABOUT 10 MPH, AT WHICH TIME A FENCE WIRE BROKE THE WIND SCREEN, AS THE ENG (AT IDLE) QUIT. THE ACFT CAME TO A HALT. I CHKED BOTH PAX AND THEY HAD NO INJURIES. I SECURED THE ENG AND EQUIP AND GOT OUT OT SURVEY THE DAMAGE. THE LEFT LIFT STRUT WAS BENT ON THE FORWARD PORTION FROM APPARENTLY HITTING A METAL POST. THE WIND SCREEN STRUTS OVER THE GLARE SHIELD PANEL WERE BENT AND 1 SIDE OF THE PROP WAS BENT (TWISTED). ALL OTHER AREAS WERE UNTOUCHED; I.E., WINGS, LNDG GEAR, FUSELAGE AND EMPENNAGE WERE UNDAMAGED. AFTER SURVEYING THE ACFT AND CHKING TO MAKE SURE THE PAX WERE STILL OK, I WENT TO THE FBO'S OFFICE TO GET HELP. THE WX LOOKED LIKE IT MIGHT PRODUCE A RAIN SHOWER AT ANY TIME THAT COULD POSSIBLY DAMAGE RADIO EQUIP OR MAKE THE TASK OF PULLING THE ACFT OUT EXTREMELY DIFFICULT. THE FBO WAS NOT AT THE OFFICE, SO I CLOSED OUT MY FLT PLAN WITH FT DODGE FSS AND FOUND A MAN WORKING ON AN ACFT IN 1 OF THE HANGARS. WE EXAMINED THIS POS OF THE ACFT IN RELATION TO THE FENCE AND HILL, THEN HE WENT TO GET A TRACTOR AND ROPE. I UNLOADED THE BAGGAGE AND WENT BACK TO THE FBO'S OFFICE WHERE THE PAX HAD GONE. WHEN I GOT TO THE FBO'S OFFICE, THE FBO HAD RETURNED. HE MENTIONED THAT HE HAD NOTIFIED THE STATE THAT THE RWY THAT I HAD USED WAS CLOSED (NOT ACCORDING TO MY FLT GUIDE OR NOTAM BRIEF). WE OBTAINED A SMALL (1500 LBS) TRACTOR AND PULLED THE ACFT AWAY FROM THE FENCE W/O FURTHER DAMAGE. WE PLACED THE ACFT IN A VACANT HANGAR TO PROTECT IT FROM THE ELEMENTS. WE (MYSELF AND PAX) OBTAINED TRANSPORTATION BACK TO AMES, IA. I TRIED TO CALL FAA VIA THE 1-800 # EARLY THE NEXT MORNING. I WAS ABLE TO MAKE CONTACT BY LATE MORNING VIA FSS. I GAVE MY RPT, THE NAME OF THE MECH I WOULD DISPATCH TO REPAIR THE ACFT, THE CSQ FBO AND THE PERTINENT DETAILS. I ALSO NOTIFIED MY INSURANCE AGENT AND MY EMPLOYER. I BELIEVE THE VARIABLE WINDS AND MUDDY FIELD (THEY HAD RECEIVED 5' OF RAIN) WERE THE PRIMARY CAUSES OF THE OVERRUN. A FRONTAL PASSAGE WAS EXPERIENCED WHICH MADE THE RWY TO BE USED QUESTIONABLE. BEING ABLE TO TALK TO SOMEONE ON A UNICOM WOULD HAVE BEEN EXTREMELY HELPFUL.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.