NYC00FA229 · Cessna 182RG
Cessna 182RG · Accident: in flight collision with object during initial climb
From 2M0 to an unrecorded destination
Event
- NTSB case
- NYC00FA229
- 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
- 0
- 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 182RG
- Aircraft type
- Cessna 182
- 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
- N3674C
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From 2M0To not recorded
- 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
- First occurrenceThe 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
- In flight collision with object
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Altitude/clearance, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot conducted a preflight inspection, then he, and three passengers boarded the airplane for a local flight. The airplane was configured with 20 degrees flaps, and began its takeoff roll from the end of the runway. According to a survivor, the takeoff took 'three quarter or better' of the 3,000-foot runway, although the engine 'sounded wide open,' and never sputtered or backfired. After takeoff, it appeared to the survivor that the airplane was going to 'just miss' a line of trees. However, its landing gear hit the tops of a tree, about 80 to 100 feet above the runway surface, and 900 feet from the runway's departure end. The airplane then hit the tops of another tree about 130 feet beyond the first tree, crossed some power lines, stalled, and spun to the ground. There was no evidence of pre-accident airframe or engine malfunction. The airport did not have refueling services. Exact takeoff weight could not be determined; however, at maximum gross weight, performance data indicated that the takeoff roll would have been 1,065 feet, and the total distance to clear a 50-foot obstacle would have been 2,060 feet. Winds during the takeoff were from abeam, about 6 knots.
Probable cause
The pilot's failure to clear trees, for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC00FA229
- Event ID
- 20001212X21824
- Case number
- NYC00FA229
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: f6f68382525c55c33a953fbc205cd558cc2cb7b4da985e1537e545e8bdf91ecd; retrieved 2026-09-20T20:55:29.144Z.