# Incident 19990803025169I: Piper PA32RT300T, Barstow, CA, August 3, 1999 - Type: FAA incident report (Accident/Incident Data System), as reported - Date: August 3, 1999, 07:13 local time - Place: Barstow, CA - Airport: Ludlow - Phase of flight: Normal Cruise - Operating rules: General operating rules (Part 91) - Location: 34.7288° N, 116.1587° W: Placed by OpenAirDocs at LUDLOW (5CA4), within about a mile (OpenAirDocs) - Nearby events: https://openairdocs.org/map.md?lat=34.7288&lon=-116.1587&mi=10 - Aircraft: N22467, a cancelled registration (https://openairdocs.org/deregistered/N22467-2004-08-28) (OpenAirDocs) - Registry model: Piper PA-32RT-300T (registry code 7103216, https://openairdocs.org/model/piper-pa-32rt-300t) (OpenAirDocs) - Registry engine: Lycoming TI0-540 series (registry code 41533, https://openairdocs.org/engine/lycoming-ti0-540-series) (OpenAirDocs) - Reported make and model: PIPER PA32RT300T - People aboard: 3 - Fatal injuries: 0 - Pilot flight hours: 700 total, 30 in this make and model, 55 in the last 90 days - FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/) - Page: https://openairdocs.org/incident/19990803025169I ## Narrative As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^. (-23) ON AUGUST 3, 1999, AT APPROX. 0713 HOURS PACIFIC DAYLIGHT TIME, PIPER PA-32RT-300T, N22467, MADE AN UNEVENTFUL FORCED LANDING AT LUDLOW AIRPORT NEAR BARSTOW, CALIFORNIA, DUT TO A SUDDENT LOSS OF ENGINE POWER. THE PRIVATE PILOT AND HIS TWO PASSENGERS WERE ENROUTE FROM SEDONA, ARIZONA TO BURBANK, CALIFORNIA. AT AN ALTITUDE OF 12,000 FEET AND ABOUT FORTY-FIVE MINUTES INTO THE FLIGHT THE ENGINE SUDDENTLY STARTED TO RUN ROUGH. THE PILOT INFORMED CENTER OF HIS PROBLEM AND ALTHOUGH HIS ENGINE WAS CONTINUING TO RUN HE COULD HOLD HIS ALTITUDE AND WOULD NOT BE ABLE TO REACH DAGGETT. CENTER INFORMED THE PILOT THAT HE WAS ONLY A FEW MILES FROM LUDLOW AIRPORT. THE PILOT LOCATED THE FIELD AND MADE AN UNEVENTFUL LANDING. THE PILOT WAS ABLE TO OBTAIN THE SERVICES OF A MECHANIC AND AFTER EXPLAINING THE ENGINE SYMPTOMS DURING THE DESCENT, EXTREME DIFFERENCES IN CYLINDER HEAD TEMPERATURES, THE MECHANIC WAS ABLE TO RESOLVE THE PROBLEM. THE MECHANIC REPLACED THE NUMBER 4 FUEL INJECTOR LINE WHICH HAD BROKEN OFF AT THE BRAZED END WHERE THE LINE CONNECTS TO THE INJECTOR. THE MECHANIC INSPECTED THE REMAINING FUEL INJECTOR LINES AND FOUND NO PROBLEMS. HE ACCOMPLISHED THE REQUIRED ENGINE RUNS AFTER THE REPAIR, MADE THE NECESSARY MAINTENANCE ENTRIES AND APPROVED THE AIRCRAFT FOR RETURN TO SERVICE. THE AIRCRAFT SUSTAINED NO DAMAGES AS A RESULT OF THIS INCIDENT AND THERE WERE NO INJURIES TO THE PILOT OR THE TWO PASSENGERS. THE PILOT STATED THAT HE WAS GOING TO FILE AN M OR D. ## Other reports on N22467 (2) Matched to the same aircraft by N-number and date. - [Accident 20010516009129A](https://openairdocs.org/incident/20010516009129A), May 16, 2001: Piper PA32RT300T (N22467), Paulden, AZ, Substantial damage. (.19)On may 16, 2001, about 1830 hours mountain standard time, a Piper PA-32RT-300T, N22467, operated by the pilot was substantially damaged during an… - [Incident 19970915036439I](https://openairdocs.org/incident/19970915036439I), Sep 15, 1997: Piper PA32RT300T (N22467), Homestead, FL, Minor damage. (-23)On September 15, 1997, Mr. Traville houston, pilot of aircraft N22467, a Piper lance, 32R-300T, landed with the left gear collapsing and minor damage… From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record. --- 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.