# NTSB CHI04CA106: Piper PA-28-180, N40RT, Columbia, MO, April 15, 2004 - Type: NTSB accident investigation - Classification: Accident · No injuries · Data collection · Final report - Date: April 14, 2004, 20:00 local (Apr 15, 2004, 01:00 UTC) - Place: Columbia, MO - Coordinates: 39.019321, -92.300933 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=39.0193&lon=-92.3009&mi=10 - Phase of flight: [Enroute](https://openairdocs.org/ntsb-phases/400) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 1 uninjured - Status: Completed, report June 30, 2004 - Report: Approved by Office Director - Parties: Kansas City, MO, FSDO - NTSB case key (mKey): 59113 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=CHI04CA106 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/59113/pdf - Page: https://openairdocs.org/ntsb/CHI04CA106 ## Probable cause The pilot inadvertently became lost and over flew his destination in cruise flight and selected an unsuitable landing area for his precautionary landing. Factors were the rough/uneven terrain, the barbed wire fence, and the fence post encountered during the precautionary landing. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Miscellaneous/other, cruise - became lost/disoriented - inadvertent, pilot in command (cause) - On ground/water encounter with terrain/water, emergency landing - unsuitable terrain or takeoff/landing/taxi area - selected, pilot in command (cause) - terrain condition - rough/uneven (contributing factor) - On ground/water collision with object, emergency landing - object - fence (contributing factor) - object - fence post (contributing factor) ## Analysis The airplane sustained substantial damage on impact with terrain during a precautionary landing. The pilot reported that he checked weather, filed a flight plan, performed a preflight, and verified that both tanks were full. The pilot stated that the first fuel tank switch was completed 12 minutes after departure and the remaining tank switches were completed on 15 to 17 minute balanced intervals. The pilot stated that he over flew his destination and turned around toward a known city. The pilot stated, "The left tank ran out of fuel, and, I reacted automatically & immediately turned on the electric fuel pump then switched from the left to the right tank - the engine fired up right away. I thought about issuing a May-Day call, but, decided not to because [Air Traffic Control] lost radar contact with me at 4000ft, and, I was at 3500. I did not want to waste fuel climbing or waste time to set up radios and communicate -started thinking about my aviate, navigate, communicate priorities. I had the radial to track back to a known airport location, Hannibal, but, I began to doubt if I had the fuel to get there. This logic hinged on the fact that I had been religious about keeping the tanks balanced. If I had emptied the left, regardless of why it emptied prematurely, the right tank should be no more than 15 minutes behind it. Figured Hannibal was at least 15 minutes out with Monroe City closer, but, neither in view. To greatly compound matters, the sun was well on its way to setting. Guessed I might have no more than 5 or 10 minutes of light left. Scanned around again for an airport - none found. Started looking for a place to make an emergency landing. ... Decided to go with my 1st choice pasture/hay field with known surface. Next, thought I heard a burp from the engine as the field approached. This made it easier to commit to the precautionary landing. ... The field was not long enough, though. I rolled into scrub brush and a barbed wire fence with metal fence posts." The pilot reported no mechanical malfunctions associated with the airplane in reference to the flight. ## Factual narrative On April 14, 2004, about 2000 central daylight time, a Piper PA-28-180, piloted by a commercial pilot, sustained substantial damage on impact with terrain during a precautionary landing near Columbia Missouri. The personal flight was operating under 14 CFR Part 91. Visual meteorological conditions prevailed at the time of the accident. An Instrument Flight Rules (IFR) flight plan had been filed, activated, and was canceled prior to the intended destination of the Monroe City Regional Airport (K52), near Monroe City, Missouri. The pilot reported no injuries. The flight originated from the Mason Jewett Field Airport, near Mason, Michigan, about 1605 and was en-route to K52 when the precautionary landing was performed. The pilot reported that he checked weather and it was Visual Flight Rules (VFR) weather the whole day. He said that he "entered intended flight plan into the DUATS [Direct User Access Terminal Service] flight planner - ran several scenarios with different destinations and cruise altitudes. Checked my DUATS PA28-180C performance profile - no problems noted - used profile as-is. Shortened route and selected Monroe City (K52) as intended fuel stop." He stated that he performed a preflight and verified that both tanks were full. The pilot stated that he the first fuel tank switch was completed 12 minutes after departure and the remaining tank switches were completed on 15 to 17 minute balanced intervals. The pilot stated: Near Quincy, ATC [Air Traffic Control] cleared me to 4000ft. Richened mixture for descent and pulled the power back. ... Shortly after leveling, the controller radioed that she had lost radar contact. She wanted my DME from the Quincy VOR. Had view of the Quincy airport slightly ahead and mostly on the right, so, based on my chart, reported that I was negative DME, but, estimated that I was about 5 from the VOR. Proceeded to the VOR, as, it was intention to track the 233 deg Quincy radial per the VOR/DME-A approach into Monroe City. Crossed over the VOR, turned and intercepted the 233 radial. Cancelled IFR a few minutes later. While tracking the 233 deg radial, noted the time as Hannibal passed on my left: clock dials at 1227 - noted in my head that I had exceeded my planned ETA and was not at my destination. Fuel gages showed more than an hour's fuel left. Still tracking the radial, I remember switching tanks again at clock dials 12:40.(Note: the analog clock in N40RT was set to UTC time.) Continued scanning for an airport, none to be found - a larger town in view to the south with a river beyond it (later verified as Columbia). Decided to make a 180 deg turn, track 233 deg radial back toward Hannibal. Completed the 180 then twisted the reciprocal heading on the VOR. The left tank ran out of fuel, and, I reacted automatically & immediately turned on the electric fuel pump then switched from the left to the right tank - the engine fired up right away. I thought about issuing a May-Day call, but, decided not to because ATC lost radar contact with me at 4000ft, and, I was at 3500. I did not want to waste fuel climbing or waste time to set up radios and communicate -started thinking about my aviate, navigate, communicate priorities. I had the radial to track back to a known airport location, Hannibal, but, I began to doubt if I had the fuel to get there. This logic hinged on the fact that I had been religious about keeping the tanks balanced. If I had emptied the left, regardless of why it emptied prematurely, the right tank should be no more than 15 minutes behind it. Figured Hannibal was at least 15 minutes out with Monroe City closer, but, neither in view. To greatly compound matters, the sun was well on its way to setting. Guessed I might have no more than 5 or 10 minutes of light left. Scanned around again for an airport - none found. Started looking for a place to make an emergency landing. The clinching factor was the impending darkness. Flew Northbound away from the town toward less density. ... Decided to go with my 1st choice pasture/hay field with known surface. Next, thought I heard a burp from the engine as the field approached. This made it easier to commit to the precautionary landing. ... After clearing a bump or rise ahead in the field, I forced the plane down, bounced twice, and put the brakes on hard while rolling on the ground. The field was not long enough, though. I rolled into scrub brush and a barbed wire fence with metal fence posts The pilot reported no mechanical malfunctions associated with the airplane in reference to the flight. At 1954, the recorded Columbia Regional Airport, near Columbia, Missouri, weather was: Wind 140 at 5 knots: visibility 10 statute miles; sky condition clear; temperature 16 degrees C; dew point -1 degree C; altimeter 30.05 inches of mercury. ## Aircraft - Registration: [N40RT](https://openairdocs.org/deregistered/N40RT-2013-06-11), registration cancelled 2013-06-11, S/N 28-4175, built 1967 (OpenAirDocs) - Reported make and model: Piper PA-28-180 - Registry model: [Piper PA-28-180](https://openairdocs.org/model/piper-pa-28-180) (registry code 7102808) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 28-4175 - Airframe hours: 4888 - Engines: Lycoming O-360-A4A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Michael Orlando Reardon - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 3, 2003, 53 hours before - Departed: TEW, MASON, MI - Destination: K52, MONROE CITY, MO - Flight plan: IFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 35; injuries: none; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, valid medical--w/ waivers/lim; last flight review December 11, 2003; seat: left; flight hours: 628 total, 436 in this make and model, 547 as pilot in command, 29 in the last 90 days, 29 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Dusk - Wind: 140° at 5 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 61 °F, dew point 30 °F - Altimeter: 30.04 inHg - Observed at: COU ## 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 20040414008519A](https://openairdocs.org/incident/20040414008519A), Apr 14, 2004: Piper PA28180, Columbia, MO, Substantial damage. (-23) The pilot overflew his intended destination, experienced engine power loss, restarted the engine and elected to make a precautionary landing. The rollout… 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.