OpenAirDocs.org

20060621010739I

Incident
Open the Markdown

FAA incident report · Cessna 172B · Anna, TX · June 21, 2006

FAA Aviation Safety Information Portal

© OpenStreetMap
Date
June 21, 2006 · 16:00 local
Place
Anna, TX
Phase of flight
Fcd/Prec Ldg From Cruise
Operating rules
General operating rules (Part 91)
Aircraft
N7876X
Reported as
Cessna 172B
Reported engine
Continental O300*
People aboard
1
Fatal injuries
0
Pilot’s flight hours
424 total424 in this make and model10 in the last 90 days
N7876XRegistered now · Cessna 172BS/N 17248376 · Built 1961Airframe modelCessna 172BEngine modelContinental 0-300 seriesReciprocating

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) Inspector's statement: my name is privacy data omitted I am employed as an aviation safety inspector by the federal aviation administration, southwest region, dallas flight standards district office, dallas, Texas 75235. As the accident standby person for the office on June 21, 2006, I was contacted by the regional comm. Center at 17:04 hours that an aircraft had reported to dfw control that he was having engine trouble and was declaring an emergency. The pilot then reported that he was safely on the ground. The dfw control then contacted the regional comm. Center. A link was made between the comm. Center, myself and a sergeant privacy data omitted of the Texas department of public safety (dps). Sgt. privacy data omitted Stated that aircraft was located in a field near county road 218 off of state road 3356. I then left my residence at about 17:30 hours and arrived at the aircraft at around 19:10 hours. Persons at the site were trooper privacy data omitted of the Texas highway patrol (dps), the pilot privacy data omitted and privacy data omitted. privacy data omitted Identified himself as the owner/pilot and privacy data omitted identified himself as a local mechanic that had recently worked on the aircraft. The aircr aft is identified as a Cessna model 172B, registration #N7876X, serial number 17248376. The pilot privacy data omitted made the following statement to me: I have been having trouble with fuel flow to the engine and had taken it to privacy data omitted in sherman, Texas to have it worked on. The fuel lines, vent lines and selector valve were blown out and flushed. We thought the problem had been solved so I took the airplane and flew in the pattern at sherman doing touch and go's for about 30 minutes with no problems. I then started to return to my home base which is dallas north airport (F69). After about 15 minutes of flying, the engine started to run rough so I pumped the throttle a few times. It helped the engine some only momentarily and it ran rough again. I then declared an emergency and located a grass field and executed an approach, touching down about a third of the way down the field. The aircraft was almost stopped when it went into a barbed wire fence, stopping about 15 feet past the fence into a plowed field. The local owner used his tractor and we moved the aircraft back to the grass field. No visible damage other than a few paint scratches were observed on the aircraft. I looked the aircraft over and observed a few scratches in the paint on the right hand stabilizer as the only physical damage. privacy data omitted Then started the aircraft and ran it for about 5 minutes to include a maximum power run. The aircraft ran fine. The pilot privacy data omitted and privacy data omitted both stated that they would do further investigation of the problem before attempting to move the aircraft. I then returned procession of the aircraft to the owner, the pilot privacy data omitted and departed the scene. All available information was called into the southwest comm. Center at 19:48 hours. I arrived back at my residence at 21:30 hours.

As the FAA filed it

(-23) INSPECTOR'S STATEMENT: MY NAME IS ^PRIVACY DATA OMI^ I AM EMPLOYED AS AN AVIATION SAFETY INSPECTOR BY THE FEDERAL AVIATION ADMINISTRATION, SOUTHWEST REGION, DALLAS FLIGHT STANDARDS DISTRICT OFFICE, DALLAS, TEXAS 75235. AS THE ACCIDENT STANDBY PERSON FOR THE OFFICE ON JUNE 21, 2006, I WAS CONTACTED BY THE REGIONAL COMM. CENTER AT 17:04 HOURS THAT AN AIRCRAFT HAD REPORTED TO DFW CONTROL THAT HE WAS HAVING ENGINE TROUBLE AND WAS DECLARING AN EMERGENCY. THE PILOT THEN REPORTED THAT HE WAS SAFELY ON THE GROUND. THE DFW CONTROL THEN CONTACTED THE REGIONAL COMM. CENTER. A LINK WAS MADE BETWEEN THE COMM. CENTER, MYSELF AND A SERGEANT ^PRIVACY^ OF THE TEXAS DEPARTMENT OF PUBLIC SAFETY (DPS). SGT. ^PRIVACY^ STATED THAT AIRCRAFT WAS LOCATED IN A FIELD NEAR COUNTY ROAD 218 OFF OF STATE ROAD 3356. I THEN LEFT MY RESIDENCE AT ABOUT 17:30 HOURS AND ARRIVED AT THE AIRCRAFT AT AROUND 19:10 HOURS. PERSONS AT THE SITE WERE TROOPER ^PRIVACY DATA O^ OF THE TEXAS HIGHWAY PATROL (DPS), THE PILOT ^PRIVACY DATA OMITTED^ AND ^PRIVACY DATA OM^. ^PRIVACY DAT^ IDENTIFIED HIMSELF AS THE OWNER/PILOT AND ^PRIVACY DA^ IDENTIFIED HIMSELF AS A LOCAL MECHANIC THAT HAD RECENTLY WORKED ON THE AIRCRAFT. THE AIRCR AFT IS IDENTIFIED AS A CESSNA MODEL 172B, REGISTRATION #N7876X, SERIAL NUMBER 17248376. THE PILOT ^PRIVACY DAT^ MADE THE FOLLOWING STATEMENT TO ME: I HAVE BEEN HAVING TROUBLE WITH FUEL FLOW TO THE ENGINE AND HAD TAKEN IT TO ^PRIVACY DA^ IN SHERMAN, TEXAS TO HAVE IT WORKED ON. THE FUEL LINES, VENT LINES AND SELECTOR VALVE WERE BLOWN OUT AND FLUSHED. WE THOUGHT THE PROBLEM HAD BEEN SOLVED SO I TOOK THE AIRPLANE AND FLEW IN THE PATTERN AT SHERMAN DOING TOUCH AND GO'S FOR ABOUT 30 MINUTES WITH NO PROBLEMS. I THEN STARTED TO RETURN TO MY HOME BASE WHICH IS DALLAS NORTH AIRPORT (F69). AFTER ABOUT 15 MINUTES OF FLYING, THE ENGINE STARTED TO RUN ROUGH SO I PUMPED THE THROTTLE A FEW TIMES. IT HELPED THE ENGINE SOME ONLY MOMENTARILY AND IT RAN ROUGH AGAIN. I THEN DECLARED AN EMERGENCY AND LOCATED A GRASS FIELD AND EXECUTED AN APPROACH, TOUCHING DOWN ABOUT A THIRD OF THE WAY DOWN THE FIELD. THE AIRCRAFT WAS ALMOST STOPPED WHEN IT WENT INTO A BARBED WIRE FENCE, STOPPING ABOUT 15 FEET PAST THE FENCE INTO A PLOWED FIELD. THE LOCAL OWNER USED HIS TRACTOR AND WE MOVED THE AIRCRAFT BACK TO THE GRASS FIELD. NO VISIBLE DAMAGE OTHER THAN A FEW PAINT SCRATCHES WERE OBSERVED ON THE AIRCRAFT. I LOOKED THE AIRCRAFT OVER AND OBSERVED A FEW SCRATCHES IN THE PAINT ON THE RIGHT HAND STABILIZER AS THE ONLY PHYSICAL DAMAGE. ^PRIVACY DA^ THEN STARTED THE AIRCRAFT AND RAN IT FOR ABOUT 5 MINUTES TO INCLUDE A MAXIMUM POWER RUN. THE AIRCRAFT RAN FINE. THE PILOT ^PRIVACY DAT^ AND ^PRIVACY DA^ BOTH STATED THAT THEY WOULD DO FURTHER INVESTIGATION OF THE PROBLEM BEFORE ATTEMPTING TO MOVE THE AIRCRAFT. I THEN RETURNED PROCESSION OF THE AIRCRAFT TO THE OWNER, THE PILOT ^PRIVACY DAT^ AND DEPARTED THE SCENE. ALL AVAILABLE INFORMATION WAS CALLED INTO THE SOUTHWEST COMM. CENTER AT 19:48 HOURS. I ARRIVED BACK AT MY RESIDENCE AT 21:30 HOURS.