ERA12FA327 · Mooney M20J
Mooney M20J · Accident: controlled flight into terrain/object (CFIT) during initial climb
From Spring Hill Airport (70N) to Republic Airport (FRG)
Event
- NTSB case
- ERA12FA327
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 2 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Mooney M20J
- Aircraft type
- Mooney M20
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N9154K
- Operator
- Patrick J. Sheridan · private individual
- Onboard fatalities
- Unknown
- Route
- From Spring Hill Airport (70N), Sterling, PATo Republic Airport (FRG), Farmingdale, NY
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Initial climb
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Controlled flight into terrain/object (CFIT)
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Environmental issues › Operating environment
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot landed at the airport for the first time, and he and two passengers went to dinner with family members. They returned to the airport after dark for the return flight to the pilot’s home base. According to the surviving passenger, the pilot initiated the takeoff roll from a taxiway intersection and did not utilize the entire runway. The 2,478 foot-long runway had a 2.4 percent upslope in the takeoff direction, with a prominent hill and trees located past the departure end. The airplane became airborne at the runway numbers, which were just before the displaced threshold, and the stall warning horn sounded immediately after liftoff. The pilot attempted to climb above the trees; however, the left wing struck a tree, and the airplane crashed into the woods about 0.37 miles past the departure end of the runway. The airplane impacted the ground inverted and caught fire. Examination of the airframe and engine revealed no evidence of a pre-impact mechanical malfunction or failure. According to the aircraft manufacturer, the expected takeoff roll for the airplane at the time of the accident was about 1,490 feet on a level runway, given a gross weight at takeoff of 2,714 pounds. Maximum gross weight for the airplane was 2,900 pounds.
The surviving passenger reported that the pilot did not utilize a checklist and did not complete any weight and balance calculations. The pilot should have aborted the takeoff when he realized he wasn’t going to liftoff in time to clear the trees.
Probable cause
The pilot’s decision to take off on an uphill slope without utilizing the entire available runway, and his failure to abort the takeoff when he realized he wasn’t going to liftoff in time to clear the trees at the end of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA12FA327
- Event ID
- 20120510X63101
- Case number
- ERA12FA327
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2012-05-10.
- API snapshot SHA-256: a592968ededcaf93e38329c919d0e4a6502bf0eb1f76e671514c14577de98b6e; retrieved 2026-09-13T22:21:35.078Z.