NYC88FA143 · Bell 206B
New York City Police Dept Bell 206B · Accident: hard landing
Event
- NTSB case
- NYC88FA143
- 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
- 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
Bell 206B
- Aircraft type
- Bell 206
- Category
- Helicopter
- 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
- N39071
- Operator
- New York City Police Dept
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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
- Landing · flare/touchdown
- 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
- Hard landing
- 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 › Control interference, inadvertent
- Pilot in command › Procedures/directives, not followed
- Pilot in command › Throttle/power control, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE BELL 206B WAS BEING FLOWN ON A HELICOPTER RATING RIDE WITH THE PIC IN THE RIGHT SEAT AND AN FAA INSPECTOR IN THE LEFT SEAT. THE ORAL WAS SATISFACTORY AND THE FLIGHT CHECK PROGRESSED TO AUTOROTATIONS. THE FIRST ONE WAS LONG, THE SECOND SHORT. ON THE THIRD ONE, WHICH WAS ALSO SHORT, THE FAA INSPECTOR COMMANDED A GO-AROUND. THE HELICOPTER CONTINUED TO DESCEND, AND THE FAA INSPECTOR TRIED TO ROLL ON THE THROTTLE BUT IT WOULD NOT MOVE. A LOW ROTOR RPM SITUATION DEVELOPED AND THE HELICOPTER MADE A HARD LANDING WITH THE TAILBOOM BEING STRUCK BY THE MAIN ROTOR BLADES. THE PIC SAID HE ROLLED ON THE THROTTLE. THE FAA INSPECTOR SECURED THE ENGINE AFTER THE ACCIDENT HE SAID HE REMEMBERED THE THROTTLE BEING AT FLIGHT IDLE WHEN HE SHUT IT DOWN. EXAMINATION OF THE AIRCRAFT SHOWED THAT THE THROTTLE COULD BE HELD WITH A TIGHT GRIP ON ONE SIDE MAKING IT DIFFICULT TO BE MOVED FROM THE OTHER SIDE. NO EVIDENCE OF AN ENGINE OR THROTTLE MALFUNCTION WAS FOUND.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC88FA143
- Event ID
- 20001213X25795
- Case number
- NYC88FA143
- 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: b5f7ab5d32f4457bccdc41e6df5c27735c24c1da70ee032b47b252b3d2b53cb5; retrieved 2026-09-22T00:34:04.284Z.