ASN Wikibase Occurrence # 176309
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Saturday 3 April 2004 |
| Time: | 09:00 |
| Type: |  Piper PA-32R-300 |
| Owner/operator: | Private |
| Registration: | N47976 |
| MSN: | 32R-7880030 |
| Year of manufacture: | 1977 |
| Total airframe hrs: | 5083 hours |
| Fatalities: | Fatalities: 0 / Occupants: 2 |
| Aircraft damage: | Substantial |
| Category: | Accident |
| Location: | Georgetown, TX -
 United States of America
|
| Phase: | Landing |
| Nature: | Private |
| Departure airport: | Houston, TX (DWH) |
| Georgetown, TX (GTU) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
Following a loss of engine power in the single-engine airplane, the 1,050-hour pilot initiated a forced landing while on approach to Runway 36. The pilot initiated a 400-foot per minute descent, reduced power to 23 inches of manifold pressure, and switched the fuel selector from the left to the right fuel tank. Upon reaching a pattern altitude of 1,800 feet approximately four miles west of his intended destination, he entered a tight right downwind for Runway 36. When the airplane was abeam the runway numbers, the airspeed was 10 knots above the landing gear extension speed, so he reduced manifold pressure to 18 inches. The pilot turned on the fuel boost pump, and pushed the mixture and prop controls forward. He extended the downwind leg to further reduce speed. While turning base, he extended the landing gear and pushed the throttle forward, but the engine would not respond. However, he does not recall the RPM setting. The pilot was unable to maintain altitude, so he reduced airspeed to 80 knots, and executed a forced landing on a feeder road adjacent to Interstate 35. Prior to touchdown, he verified that the fuel boost pump was on, the fuel selector was in the detent, and the master and ignition switches were on. He also pushed the mixture and propeller controls to the full forward position. The flaps were never extended. The engine was test run with a two-bladed propeller. The fuel-injected engine was run on the airframe utilizing a provisional fuel line that was attached to the right fuel tank's inboard fitting and a plastic gas can. The engine started and ran normal from idle to 1,500 RPM without interruption. There was no mixture rise observed when leaning the mixture with the engine running at 1,500 RPM. A magneto check was conducted at 1,500 RPM. The engine ran smooth with the RPM dropping approximately 100-125 RPM on both the left and right magneto positions. The cockpit fuel pressure gauge was sluggish and indicated slightly low. A test gauge was installed that indicated 20 psi at idle with the boost pump off and 22 psi with the boost pump on. At 1,500 RPM, the test gauge indicated 25 psi with the boost pump on or off. The fuel vents were also absent of debris. The induction air filter and induction system "appeared" normal and unobstructed. No mechanical anomalies were noted that would have precluded normal engine operation.
Probable Cause: The loss of engine power for undetermined reasons. A contributing factor was the lack of suitable terrain for the forced landing.
Accident investigation:
 |
|
Sources:
NTSB: https://www.ntsb.gov/_layouts/ntsb.aviation/brief.aspx?ev_id=20040428X00527&key=1
Location
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 23-May-2015 14:39 | Noro | Added |
| 21-Dec-2016 19:30 | ASN Update Bot | Updated [Time, Damage, Category, Investigating agency] |
| 07-Dec-2017 17:52 | ASN Update Bot | Updated [Cn, Operator, Other fatalities, Departure airport, Destination airport, Source, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation