ERA09CA270 · Cessna 150G
Cessna 150G · Accident: collision during takeoff/landing on approach
From Kingston-Ulster Airport (20N) to Kingston-Ulster Airport (20N)
Event
- NTSB case
- ERA09CA270
- 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
- 0 · 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
Cessna 150G
- Aircraft type
- Cessna 150
- 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
- N2792S
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Kingston-Ulster Airport (20N), Kingston, NYTo Kingston-Ulster Airport (20N), Kingston, 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
- Approach · VFR pattern final
- 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
- Collision during takeoff/landing
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
On final approach to Runway 15, approximately 200 feet prior to the runway, the pilot determined that the airplane was "slightly high," and reduced power to aid in the descent. The pilot stated that the airplane then descended "too low," and although he added full power and applied back pressure on the yoke, the tail of the airplane contacted trees. The pilot was subsequently unable to control the airplane, which made a descending right turn. The airplane struck a fence during the descent, and came to rest on grass to the right of the threshold of Runway 15. The pilot stated that after he exited the airplane, he observed a "1 inch diameter branch wedged into the left elevator." According to the pilot, if he had kept his speed and altitude "within safer margins" the accident would not have occurred. The pilot had 72 hours of flight experience in the accident airplane, and had flown 1 hour in the previous 30 days. The weather reported at the accident airport, 20 minutes after the accident, included winds from 190 degrees at 9 knots, gusting to 13 knots. The pilot described the winds as being "light" and "intermittent" with "occasional gusts." Examination of the airplane revealed substantial damage to the right wing, and no preimpact mechanical anomalies were noted.
Probable cause
The pilot's failure to maintain clearance from trees during approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09CA270
- Event ID
- 20090427X64827
- Case number
- ERA09CA270
- 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: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: d801e363dc2c05a2fb49f2e521699c074259b219e831076cdaa4de8096bd10dd; retrieved 2026-09-15T10:59:30.125Z.