20000712010029A

Accident · Substantial damage

FAA accident report · Piper PA-23-160 · Rio Grande City, TX · July 12, 2000

Date
July 12, 2000 · 13:30 local
Place
Rio Grande City, TX
Airport
Starr County Airport
Phase of flight
Forced/Precautionary Landing
Operating rules
General operating rules (Part 91)
Damage
Substantial damage
Aircraft
N4322P
NTSB investigation
NTSBFTW00LA205
Reported as
Piper PA23160
Reported engine
Lycoming O320B3B
People aboard
2
Fatal injuries
0
Pilot’s flight hours
286 total

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) On take-off, both engines lost power. Aircraft impacted terrain causing major damage to aircraft. No NMAC, no fire. (.4)on July 12, 2000, approximately 1330 central daylight time, a Piper PA-23-160 twin-engine airplane, N4322P, was substantially damaged during a forced landing following a loss of engine power during takeoff climb from the Starr County Airport near Rio Grande City, Texas. The airplane was owned and operated by a private individual. The commercial pilot and his pilot-rated passenger were not injured. Visual meteorological conditions prevailed, and a flight plan was not filed for the 14 code of federal regulations part 91 positioning flight. The flight was originating at the time of the accident and was destined for the david wayne hooks airport, spring, Texas. The flight had departed corpus christi, Texas, on the day prior to the accident and was en route to mcallen, Texas, when the airplane experienced a total electrical failure. The pilot made a precautionary landing at the Starr County Airport, where he had the battery charged. However, the electrical problem was not repaired prior to departing on the day of the accident. Accordin g to the pilot, prior to departure, he performed a "through preflight and run-up check." After lift-off from runway 15, the landing gear was retracted, and a left turn was initiated. While in the turn, about 300-400 feet AGL, the left engine began "sputtering," and after a "few seconds" the engine lost power. The right engine then began to "sputter." Subsequently, the right engine lost power. The pilot executed a forced landing to a field with brush and mesquite trees. The airplane came to rest one mile north of the Starr County Airport. An FAA inspector, who responded to the accident site, reported that the fuselage was "partially separated aft of the cabin." Additionally, both wings were structurally damaged. The reason for the loss of engine power could not be determined. According to the FAA inspector, the airplane had been inspected on July 6, 2000, by another FAA inspector, who issued an aircraft condition notice for maintenance defects, which were considered to be an imminent hazard to safety. A special flight permit was required prior to operating the aircraft if corrective action had not been taken. An examination of the airplane revealed that the maintenance defects were not corrected, and a special flight permit had not been obtained. Neither the pilot nor the operator responded to requests to provide a completed pilot/operator aircraft accident report (NTSB form 6120.1/2).

As the FAA filed it

(-23) ON TAKE-OFF, BOTH ENGINES LOST POWER. AIRCRAFT IMPACTED TERRAIN CAUSING MAJOR DAMAGE TO AIRCRAFT. NO NMAC, NO FIRE. (.4)ON JULY 12, 2000, APPROXIMATELY 1330 CENTRAL DAYLIGHT TIME, A PIPER PA-23-160 TWIN-ENGINE AIRPLANE, N4322P, WAS SUBSTANTIALLY DAMAGED DURING A FORCED LANDING FOLLOWING A LOSS OF ENGINE POWER DURING TAKEOFF CLIMB FROM THE STARR COUNTY AIRPORT NEAR RIO GRANDE CITY, TEXAS. THE AIRPLANE WAS OWNED AND OPERATED BY A PRIVATE INDIVIDUAL. THE COMMERCIAL PILOT AND HIS PILOT-RATED PASSENGER WERE NOT INJURED. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND A FLIGHT PLAN WAS NOT FILED FOR THE 14 CODE OF FEDERAL REGULATIONS PART 91 POSITIONING FLIGHT. THE FLIGHT WAS ORIGINATING AT THE TIME OF THE ACCIDENT AND WAS DESTINED FOR THE DAVID WAYNE HOOKS AIRPORT, SPRING, TEXAS. THE FLIGHT HAD DEPARTED CORPUS CHRISTI, TEXAS, ON THE DAY PRIOR TO THE ACCIDENT AND WAS EN ROUTE TO MCALLEN, TEXAS, WHEN THE AIRPLANE EXPERIENCED A TOTAL ELECTRICAL FAILURE. THE PILOT MADE A PRECAUTIONARY LANDING AT THE STARR COUNTY AIRPORT, WHERE HE HAD THE BATTERY CHARGED. HOWEVER, THE ELECTRICAL PROBLEM WAS NOT REPAIRED PRIOR TO DEPARTING ON THE DAY OF THE ACCIDENT. ACCORDIN G TO THE PILOT, PRIOR TO DEPARTURE, HE PERFORMED A "THROUGH PREFLIGHT AND RUN-UP CHECK." AFTER LIFT-OFF FROM RUNWAY 15, THE LANDING GEAR WAS RETRACTED, AND A LEFT TURN WAS INITIATED. WHILE IN THE TURN, ABOUT 300-400 FEET AGL, THE LEFT ENGINE BEGAN "SPUTTERING," AND AFTER A "FEW SECONDS" THE ENGINE LOST POWER. THE RIGHT ENGINE THEN BEGAN TO "SPUTTER." SUBSEQUENTLY, THE RIGHT ENGINE LOST POWER. THE PILOT EXECUTED A FORCED LANDING TO A FIELD WITH BRUSH AND MESQUITE TREES. THE AIRPLANE CAME TO REST ONE MILE NORTH OF THE STARR COUNTY AIRPORT. AN FAA INSPECTOR, WHO RESPONDED TO THE ACCIDENT SITE, REPORTED THAT THE FUSELAGE WAS "PARTIALLY SEPARATED AFT OF THE CABIN." ADDITIONALLY, BOTH WINGS WERE STRUCTURALLY DAMAGED. THE REASON FOR THE LOSS OF ENGINE POWER COULD NOT BE DETERMINED. ACCORDING TO THE FAA INSPECTOR, THE AIRPLANE HAD BEEN INSPECTED ON JULY 6, 2000, BY ANOTHER FAA INSPECTOR, WHO ISSUED AN AIRCRAFT CONDITION NOTICE FOR MAINTENANCE DEFECTS, WHICH WERE CONSIDERED TO BE AN IMMINENT HAZARD TO SAFETY. A SPECIAL FLIGHT PERMIT WAS REQUIRED PRIOR TO OPERATING THE AIRCRAFT IF CORRECTIVE ACTION HAD NOT BEEN TAKEN. AN EXAMINATION OF THE AIRPLANE REVEALED THAT THE MAINTENANCE DEFECTS WERE NOT CORRECTED, AND A SPECIAL FLIGHT PERMIT HAD NOT BEEN OBTAINED. NEITHER THE PILOT NOR THE OPERATOR RESPONDED TO REQUESTS TO PROVIDE A COMPLETED PILOT/OPERATOR AIRCRAFT ACCIDENT REPORT (NTSB FORM 6120.1/2).

NTSB investigation

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

Other reports on N4322P · 1

Matched to the same aircraft by N-number and date.