NYC04LA213 · Cessna 185F
Cessna 185F · Accident: on ground/water collision with object during landing
From Hartford Brainard Airport (HFD) to Somerset Airport (SMQ)
Event
- NTSB case
- NYC04LA213
- 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 185F
- Aircraft type
- Cessna 185
- 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
- N29BF
- Operator
- Michael Foise
- Onboard fatalities
- Unknown
- Route
- From Hartford Brainard Airport (HFD), Hartford, CTTo Somerset Airport (SMQ), Somerville, NJ
- 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
- Landing · landing roll
- 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
- On ground/water 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
- Substantial
Cause areas
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Upon touching down on the runway, the airplane veered off the left side of the runway, struck a parked airplane, and continued into a hangar. Inside the hangar, the accident airplane struck another parked airplane, before coming to a stop. After the accident, state authorities arrested the pilot, and found a supply of prescription sedative medication in the airplane. Examination of the airplane did not reveal any mechanical abnormalities with the airframe, landing gear assembly, or the engine. Review of the pilot's medical records by the NTSB Medical Officer revealed that on the pilot's most recent application for second-class airman medical certificate, the pilot indicated "Yes" in response to the question about "Substance dependence" and "Alcohol dependence or abuse." Under "Comments on History and Findings" the pilot stated, "...involved in airplane crash. Substance abuse involved..."
Probable cause
The pilot's failure to maintain aircraft control while landing. A factor was the pilot's impairment due to the influence of non-prescribed pain medication.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC04LA213
- Event ID
- 20040930X01540
- Case number
- NYC04LA213
- 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, coordinates. 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: ccad9ec40e0d5f0439f9684d49b34e540f9d22bf251d0bf1c30a2e86e906926c; retrieved 2026-09-21T19:08:28.485Z.