# NTSB IAD05CA140: Beech BE-36, N8014T, Farmingdale, NY, September 23, 2005

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Data collection · Final report
- Date: September 23, 2005, 17:50 local (21:50 UTC)
- Place: Farmingdale, NY
- Coordinates: 40.728889, -73.41333
- Nearby events: https://openairdocs.org/map.md?lat=40.7289&lon=-73.4133&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 3 uninjured
- Status: Completed, report January 31, 2006
- Report: Approved by Office Director
- NTSB case key (mKey): 62542
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD05CA140
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/62542/pdf
- Page: https://openairdocs.org/ntsb/IAD05CA140

## Probable cause

The pilot's improper recovery from a bounced landing.

## Sequence of events

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

- Loss of control - on ground/water, landing
  - recovery from bounced landing - improper, pilot in command (cause)
- On ground/water collision with object, landing
  - object - fence

## Analysis

According to the pilot, after the airplane landed and was rolling out, he "came back" on the throttle, the engine "started to race," and the airplane veered to the right.  The pilot attempted to control the airplane by applying the brakes and left rudder, but to no avail.  The airplane then veered off the right side of the runway, through grass, then crossed a taxiway, then more grass, continued up an incline, and stopped when it struck a perimeter fence.  One witness, a student pilot, saw the airplane land "hard" and bounce two to three times during the touchdown.  A second witness, a certificated airline transport pilot, saw the airplane land "flat", with no flare, and bounce "at least three times" before veering off the runway.  A subsequent examination of the airplane, which included control continuity checks, brakes, and flight and throttle controls, revealed no pre-impact mechanical anomalies.  Weather, about the time of the accident, included clear skies and variable winds at 4 knots.

## Factual narrative

On September 23, 2005, at 1750 eastern daylight time, a Beech BE-36, N8014T, was substantially damaged when it impacted a fence during a landing roll-out at Republic Airport (FRG), Farmingdale, New York.  The certificated airline transport pilot and two passengers were not injured.  Visual meteorological conditions prevailed.  The airplane was operating on an instrument flight rules flight plan from Atlantic City Municipal/Bader Field (AIY), Atlantic City, New Jersey.  The personal flight was conducted under 14 CFR Part 91.

According to the pilot, after the airplane landed and was rolling out on runway 32, he "came back" on the throttle, the engine "started to race," and the airplane veered to the right.  The pilot attempted to control the airplane by applying the brakes and left rudder, but to no avail.

The airplane then veered off the right side of the runway, through grass, then crossed a taxiway, then more grass, continued up an incline, and stopped when it struck a perimeter fence.

According to a Federal Aviation Administration (FAA) inspector, two witnesses observed the landing.  The first was a student pilot who saw the airplane land "hard" and bounce two to three times.  The second witness, a certificated airline transport pilot, was a passenger in a corporate jet that was holding short of the runway.  That witness stated that the accident airplane landed "flat", with no flare, and bounced at least three times before veering off the right side of the runway.

The FAA inspector subsequently performed an examination of the airplane, which included control continuity checks, brakes, and flight and throttle controls, and found no pre-impact anomalies.

Weather, reported at the airport about the time of the accident, included clear skies and variable winds at 4 knots.

## Aircraft

- Registration: [N8014T](https://openairdocs.org/deregistered/N8014T-2020-12-05), registration cancelled 2020-12-05, S/N E-2561, built 1990 (OpenAirDocs)
- Reported make and model: Beech BE-36
- Registry model: [Beech A36](https://openairdocs.org/model/beech-a36) (registry code 1151604) (OpenAirDocs)
- Registry engine: [Continental IO-550 series](https://openairdocs.org/engine/continental-io-550-series) (registry code 17042, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: E-2561
- Engines: Continental IO-550 reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Registered owner: MAR-ATP of Delaware, Inc
- Airworthiness certificate: Standard, Normal
- Departed: AIY, Atlantic City, NJ
- Destination: FRG, Farmingdale, NY
- Flight plan: IFR

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot; age 75; injuries: none; airline transport; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3; flight hours: 8,700 total, 7,500 in this make and model

## Weather

- Conditions: Visual (VMC), Day

## 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 20050923032409A](https://openairdocs.org/incident/20050923032409A), Sep 23, 2005: Beech A36, Farmingdale, NY, Substantial damage. (-23) Aircraft returning to Farmingdale (frg) Republic Airport from atlantic city bader (aiy), IFR. Pilot is on a visual approach to runway 32. Upon landing on…

## Other investigations on N8014T (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 ERA19FA189](https://openairdocs.org/ntsb/ERA19FA189), Jun 8, 2019: Beech A36 (N8014T), Southold, NY, destroyed, 2 fatal. Probable cause: A total loss of engine power due to a main bearing shift and the pilot’s subsequent failure to maintain a proper glide path to the selected forced landing site. Contributing to the accident was the…

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.
