# NTSB FTW99LA154: Piper PA-30B, N7991Y, Mcalester, OK, May 28, 1999

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: May 28, 1999, 16:30 local (21:30 UTC)
- Place: Mcalester, OK
- Coordinates: 34.920078, -95.760696 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=34.9201&lon=-95.7607&mi=10
- Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 2 uninjured
- Status: Completed, report November 30, 2000
- Report: Approved by Office Director
- NTSB case key (mKey): 46424
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=FTW99LA154
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/46424/pdf
- Page: https://openairdocs.org/ntsb/FTW99LA154

## Probable cause

The pilot inadvertently stalling the airplane while attempting to avoid power lines.  Factors were the loss of power on both the left and right engines as a result of water contamination in the fuel system, the pilot's inadequate preflight procedures, and the lack of suitable terrain for the forced landing.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of engine power(total) - nonmechanical, takeoff - initial climb
  - 1 engine
  - fuel system,tank - contamination,water (contributing factor)
  - aircraft preflight - inadequate, pilot in command (contributing factor)
- Loss of engine power(partial) - nonmechanical, takeoff - initial climb
  - 1 engine
  - fuel system,tank - contamination,water (contributing factor)
  - aircraft preflight - inadequate, pilot in command (contributing factor)
- Forced landing, descent - emergency
- Loss of control - in flight, emergency descent/landing
  - terrain condition - none suitable (contributing factor)
  - maneuver to avoid obstructions - performed, pilot in command
  - object - wire,transmission
  - stall - inadvertent, pilot in command (cause)
- In flight collision with terrain/water, emergency landing after takeoff

## Analysis

Shortly after takeoff, the airplane's left engine experienced a loss of power followed soon thereafter by a partial loss of power of the right engine.  The pilot was unable to maintain altitude and made a forced landing in a field. The pilot added that he 'had to climb over power lines [and] stalled [the] aircraft.'  The pilot stated that he had refueled the airplane with 90 gallons of fuel prior to his departure.  He added that he had visually checked the fuel level prior to the departure; however, he did not sump the fuel tanks.  Fuel samples that were taken from the airplane's left and right main fuel tanks contained a fluid on the bottom of each sample, which resembled water.  A fuel sample taken from the refueling truck revealed no evidence of water contamination.

## Factual narrative

On May 28, 1999, at 1630 central daylight time, a Piper PA-30B twin-engine airplane, N7991Y, was substantially damaged during a forced landing following a loss of engine power after takeoff from the McAlester Regional Airport near McAlester, Oklahoma.  The instrument rated private pilot and his pilot rated passenger were not injured.  The airplane was owned and operated by the pilot.  Visual meteorological conditions prevailed and a flight plan was not filed for the 14 Code of Federal Regulations Part 91 personal flight destined for Oklahoma City, Oklahoma.  The cross-country flight was originating at the time of the accident.

During a telephone interview conducted by the NTSB investigator-in-charge, the pilot stated that shortly after takeoff, while climbing through 300 feet agl, the left engine "quit."  The pilot added that after attempting to restart the engine, he elected to feather the propeller.  Shortly after feathering the left propeller, the right engine started to "sputter."  The pilot stated that the right engine never completely failed; however, he was unable to maintain altitude with the sputtering right engine and elected to land the airplane, with the landing gear retracted, in a field approximately 2 miles south of the McAlester Airport.  In the enclosed Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1/2), the pilot stated that he "had to climb over power lines [and] stalled [the] aircraft."

The pilot reported that the left wing spar, outboard of the engine, was broken.  The right wing spar, outboard of the engine, was bent aft, and the empennage was separated except for a section of sheet metal attaching it to the airplane.

The pilot reported that he had refueled the airplane with 90 gallons of fuel prior to his departure.  The pilot stated that he had visually checked the fuel level prior to the departure; however, he did not sump the fuel tanks.  He added that the flight to McAlester earlier that day had been uneventful and that there were no problems with either engine.

During the recovery process, fuel samples were taken from the airplane's left and right main fuel tanks.  A half-gallon of fuel was drained from each tank into two separate 1-gallon containers.  The bottom half of the sample taken from the left main fuel tank appeared clear in color and resembled water.  The bottom 1/8th of the half-gallon fuel sample taken from the right main fuel tank appeared clear in color and also resembled water.  The remaining fluid in both samples was blue in color and resembled 100LL aviation fuel.

The FAA inspector, who responded to the accident site, stated that he examined fuel samples taken from the fixed base operator's fueling truck, from which the accident airplane was refueled, and found no evidence of water contamination.

## Aircraft

- Registration: [N7991Y](https://openairdocs.org/deregistered/N7991Y-2001-12-21), registration cancelled 2001-12-21, S/N 30-1095, built 1966 (OpenAirDocs)
- Reported make and model: Piper PA-30B
- Registry model: [Piper PA-30](https://openairdocs.org/model/piper-pa-30) (registry code 7103002) (OpenAirDocs)
- Registry engine: [Lycoming IO-320 series](https://openairdocs.org/engine/lycoming-io-320-series) (registry code 41509, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 30-1095
- Airframe hours: 4495
- Engines: Lycoming IO-320-B1A 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Freddie W. Chambers
- Registered owner: S & F Inc.
- Airworthiness certificate: Standard, Normal
- Last inspection: Annual, December 1, 1998
- Departed: MLC
- Destination: OKC, OKLAHOMA CITY, OK
- Airport: MLC, Mcalester Regional

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 57; private; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 717 total, 450 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 70° at 7 knots
- Visibility: 10 statute miles
- Lowest ceiling: none
- Temperature: 79 °F, dew point 57 °F
- Altimeter: 30.00 inHg
- Observed at: MLC, 2 nm away

## FAA reports on this event (1)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 19990528006079A](https://openairdocs.org/incident/19990528006079A), May 28, 1999: Piper PA30, Mcalester, OK, Substantial damage. N7991Y departed mlc, left engine failed, acft crashed 2 miles south of airport.(.19) on may 28, 1999, at 1630 central daylight time, a Piper PA-30 twin engine…

## Other investigations on N7991Y (2)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CHI74 EM04](https://openairdocs.org/ntsb/CHI74%20EM04), Jul 15, 1973: Piper PA-30 (N7991Y), West Branch, MI, substantial damage
- [NTSB FTW68F0515](https://openairdocs.org/ntsb/FTW68F0515), Mar 29, 1968: Piper PA-30 (N7991Y), Alexandria, LA, substantial damage

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

---
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.
