# NTSB NYC07LA183: Piper Aerostar 601P, N60801, Fort Lauderdale, FL, August 2, 2007

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: August 1, 2007, 20:00 local (Aug 2, 2007, 00:00 UTC)
- Place: Fort Lauderdale, FL
- Coordinates: 26.197221, -80.170555
- Nearby events: https://openairdocs.org/map.md?lat=26.1972&lon=-80.1706&mi=10
- Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 3 uninjured
- Status: Completed, report July 30, 2008
- Report: Approved by Office Director
- Parties: FAA/FSDO
- NTSB case key (mKey): 66384
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC07LA183
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/66384/pdf
- Page: https://openairdocs.org/ntsb/NYC07LA183

## Probable cause

The total loss of power in one engine during approach, due to a fatigue fracture of the crankshaft.

## Sequence of events

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

- Loss of engine power(total) - mech failure/malf, approach - vfr pattern - final approach
  - 1 engine - failure
  - engine assembly,crankshaft - fatigue (cause)
- Forced landing, descent - emergency
- Loss of control - in flight, emergency landing
- On ground/water collision with object, emergency landing
  - object - tree(s)

## Analysis

As the airplane turned onto final approach in the traffic pattern, at an altitude of 1,000 feet, the right engine began a violent vibration and started to lose power. The airplane was unable to maintain altitude, and the pilot attempted a forced landing to a road. As the airplane reached an altitude of approximately 300 feet, it began to lose directional control and impacted a traffic light. After touchdown, the airplane began to skid and impacted several objects on the ground before coming to rest. Metallurgical examination of the right engine revealed that it lost power due to a fatigue-fractured crankshaft. The pilot had positioned the right propeller control to feather, but the right propeller did not feather due to the fractured crankshaft. The engine was most recently overhauled 11 years prior to the accident, and the engine had accumulated 471 hours since then.

## Factual narrative

On August 1, 2007, at approximately 2000 eastern daylight time, a Piper Aerostar 601P, N60801, was substantially damaged during a forced landing to a road in Fort Lauderdale, Florida. The certificated commercial pilot and two passengers were not injured. Visual meteorological conditions prevailed and no flight plan was filed for the local flight, which departed from Fort Lauderdale Executive Airport (FXE), Fort Lauderdale, Florida. The personal flight was conducted under 14 Code of Federal Regulations Part 91.

According to the pilot, after departing runway 26, he remained in the traffic pattern for a landing. As he turned the airplane onto the final approach, at an altitude of 1,000 feet mean sea level, the right engine began a violent vibration and started to lose power. The pilot stated he advanced the mixture, propeller, and throttle levers to the full forward position, and turned the fuel boost pump on. The right engine then completely lost power and the pilot placed the propeller lever in the feathered position. He advanced the left engine throttle to full power, retracted the landing gear and established the aircraft on final approach. The airplane was unable to maintain airspeed and altitude, and the pilot decided to perform a forced landing to a road parallel to runway 26. As the airplane reached an altitude of approximately 300 feet, it began to "lose directional control," and the pilot reduced power to the left engine. The airplane impacted a traffic light prior to landing on the road. After touchdown, the airplane began to skid to the right and impacted several objects before it came to rest, and a postcrash fire ensued.

Examination of the airplane by a Federal Aviation Administration (FAA) inspector revealed the right engine cockpit controls were in the "aft position," (right propeller lever in feather position) and the right propeller was not feathered. Both wing fuel tanks were ruptured; however, evidence of fuel was present in both wings.

The right engine was disassembled, under the supervision of an FAA inspector. According to the FAA inspector, the engine crankshaft had sheared between the No. 2 and No. 3 main bearings. The engine camshaft had also sheared at the No. 5 cylinder.

The crankshaft and camshaft were sent to the National Transportation Safety Board's Materials Laboratory. Examination of the components revealed fatigue propagation over the majority of the crankshaft fracture surface. The camshaft sustained impact damage and was completely fractured in overstress bending and torsion.

Examination of the aircraft and engine logbooks revealed the most recent 100-hour inspection was completed on January 16, 2007. The most recent overhaul of the right engine was completed in July 1996, after a propeller strike incident. During the overhaul, the cylinders were "cermichrome" processed, repaired and certified. The crankshaft was "inspected and certified," and the crankcase was "repaired and certified." Since the overhaul, 11 years prior to the accident, the engine accumulated 471 hours.

Weather reported at FXE, at 1953, included wind from 240 degrees at 3 knots, 10 miles visibility, scattered clouds at 2,500 feet, overcast clouds at 15,000 feet, temperature 27 degrees Celsius (C), dew point 23 degrees C, and barometric pressure setting of 29.90 inches mercury.

## Aircraft

- Registration: [N60801](https://openairdocs.org/deregistered/N60801-2013-04-25), registration cancelled 2013-04-25, S/N 61P07448063366, built 1979 (OpenAirDocs)
- Reported make and model: Piper Aerostar 601P
- Registry model: [Piper AEROSTAR 601P](https://openairdocs.org/model/piper-aerostar-601p) (registry code 7106012) (OpenAirDocs)
- Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41530, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 61P07448063366
- Airframe hours: 2514
- Engines: Lycoming IO-540 300 lbs thrust reciprocating; Lycoming IO-540 300 lbs thrust reciprocating
- Damage: Substantial damage
- Fire: On-Ground
- Flight: Personal, Part 91
- Operator: Austin Brennen
- Registered owner: Gerald Tillman
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, January 1, 2007
- Departed: FXE, Fort Lauderdale, FL
- Destination: FXE
- Airport: FXE, Fort Lauderdale Executive, runway 26, 6,001 × 100 ft, asphalt

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 24; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; seat: left; flight hours: 1,950 total

## Weather

- Conditions: Visual (VMC), Day
- Wind: 240° at 3 knots
- Visibility: 10 statute miles
- Lowest ceiling: 15,000 ft overcast
- Temperature: 81 °F, dew point 73 °F
- Altimeter: 29.89 inHg
- Observed at: FXE

## 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 20070801824269A](https://openairdocs.org/incident/20070801824269A), Aug 1, 2007: Piper PA60601P, Fort Lauderdal, FL, Destroyed. (-23) On August 01, 2007 at approximately 2000 EST, the pilot [privacy data omitted] of N60801, a Piper PA-60-601P, serial number 61P-07448063366, was on the…

## Other investigations on N60801 (1)

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 CHI83FA138](https://openairdocs.org/ntsb/CHI83FA138), Mar 15, 1983: Piper PA-601P (N60801), Wheeling, IL, 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.
