MIA02FA144 · Piper PA-28-180
Piper PA-28-180 · Accident: total loss of engine power (non-mechanical) on approach
From 47J · Cheraw, SC to Darlington County Airport (KUDG)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- MIA02FA144
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Piper PA-28-180
- Aircraft type
- Piper PA-28
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N3450R
- Operator
- James R. Meggs · private individual
- Onboard fatalities
- Unknown
- Route Possible conflict
- From 47J · Cheraw, SCTo Darlington County Airport (KUDG), Darlington, SC
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Approach · VFR pattern downwind
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Total loss of engine power (non-mechanical)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation; Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Fluid, fuel › Starvation
- Fuel system, line › Misrouted
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot was observed walking around the airplane performing a preflight inspection before engine start. The flight departed from runway 07, and remained in the traffic pattern. When the flight was approximately three quarters down the runway on the downwind leg, witnesses heard the engine sputter and experience a loss of power. The airplane was observed to continue on the downwind leg; several witnesses reported that they perceived the flight path to be similar to a normal traffic pattern rather than turning toward the runway. The airplane became low on final approach and went out sight behind trees. The airplane impacted a tree then the ground, and came to rest upright approximately a quarter nautical mile from the approach end of runway 07. The fuel selector was found positioned to near the "right" tank position; impact damage to the selector valve attach structure was noted though no fuel stains in the area was noted. The right fuel tank was found to contain approximately 20 ounces of fuel. The left wing remained secured only by the aileron control cables but remained in close proximity to the fuselage; the fuel tank contained approximately 13 gallons of fuel. No obstructions of the fuel vent or delivery system were noted. The fuel line from the right fuel tank was routed to the forward side of the fuel selector valve, and the fuel line from the left fuel tank was routed to the aft side of the fuel selector valve. Only drops of fuel were noted in the fuel lines in the engine compartment area; no obstructions of the fuel delivery or vent systems were noted. The engine was removed from the airplane, a replacement propeller was installed, and the engine was started and operated to 2,250 rpm with no discrepancies noted. The airplane was previously involved in a partial collapse of the nose landing gear and propeller strike while landing at an airport in California; the airplane was sold to an airplane salvage company who had the wings removed. The airplane was transported to their facility, then transported and sold to the accident pilot. A mechanic performing repairs and the last annual inspection to the airplane reported the aluminum fuel lines located in the cockpit aft of the fuel selector valve were damaged to the point that he could not determine routing of the lines. Based on his perception of the illustration in the Piper Parts Catalog, and also on his belief that the fuel selector handle pointed to the forward port of the fuel selector valve when the right fuel tank was selected, he routed and connected the fuel line from the right fuel tank to the forward side of the fuel selector valve, and the fuel line from the left fuel tank to the aft side of the selector valve. On the first page of the Introduction Section of the PA-28 parts catalog, there is a note, in bold letters, which states, "UNDER NO CIRCUMSTANCES SHALL THIS CATALOG BE USED FOR RIGGING AND INSTALLATION PURPOSES." The parts catalog indicates that the fuel line from the right fuel tank should be routed to the aft side of the fuel selector valve, and the fuel line from the left fuel tank should be routed to the forward side of the fuel selector valve. The illustration of the parts catalog was difficult to ascertain the routing of fuel lines from the fuel selector valve to the tanks, but the index clearly indicated the routing. Following the repairs, fuel was added to the tanks, he checked for fuel leaks, and verified engine operation. He also test flew the airplane, and flew with the pilot a short duration. The accident pilot reportedly flew the airplane 3 or 4 times after the inspection was completed, and the airplane was also flown by a friend of the pilot a day earlier. The pilot reported before departure, the right fuel tank had 5-6 gallons and the left fuel tank had approximately 15 gallons of fuel. The flight duration was approximately 30 minutes and was flown with the fuel selector positioned to the left tank position; the selector was not moved during the flight. He did not visually inspect the tanks after landing but reported the left fuel gauge indicated approximately 10 gallons of fuel after landing; he did not note the right fuel gauge reading after landing. The owners handbook indicates that the fuel selector is to be on the proper tank for takeoff, and in the event of a loss of engine power, to position the fuel selector to the opposite tank.
Probable cause
The misrouting of the fuel lines to the fuel selector, which resulted in the use of a fuel tank with inadequate fuel supply, fuel starvation, and the loss of engine power. Contributing was the pilot's inadequate remedial action for conducting an emergency landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA02FA144
- Event ID
- 20020807X01322
- Case number
- MIA02FA144
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 0a206cccbaa139f5c1d01febc41d39776f6c60fe74ff931d86ea7134b70e6d45; retrieved 2026-09-20T19:55:57.815Z.