NYC82FHD10 · Cessna 210B
Cessna 210B · Accident: in flight collision with terrain/water during landing
From Atlantic City, NJ to Northampton, MA
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- NYC82FHD10
- 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
Cessna 210B
- Aircraft type
- Cessna 210
- 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
- N9740Y
- Operator
- Roger Bourcier
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Atlantic City, NJTo Northampton, MA
- 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
- In flight collision with terrain/water
- 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 › Gear extension, not selected
Approximate · Estimated position: the centre of Toms River, NJ, the place the record names. Not the accident site.
NTSB narrative
THE PLT REPORTED THE ACFT WAS LABORING AFTER TAKEOFF FROM ATLANTIC CITY. HE DECIDED TO CIRCLE THE FIELD (BADGER) PRIOR TO CONTINUING ON TO NORTHAMPTON, MA. UPON REACHING 3,000 FT HE STATED THE ACFT AGAIN STARTED LOSING AIRSPEED ALTHOUGH THE POWER INDICATED "24 SQUARE." A PRECAUTIONARY LANDING WAS MADE AT TOMS RIVER & THE ACFT RE-PREFLIGHTED. FINDING NOTHEING OBVIOUS HE DEPLANED HIS PASSENGERS & TOOK OFF BY HIMSELF TO CHECK ACFT PERFORMANCE. IN TURNING BASE LEG THE PROBLEM REOCCURRED. HE STATED HE LOWERED FLAP & GEAR SWITCHES. THE ACFT CAME TO A STOP WITH THE GEAR UP. THE GEAR HANDLE WAS FOUND IN THE NEUTRAL POSITION. DURING GEAR TESTS IT WAS NOTED THAT THE WARNING HORM DID NOT OPERATE WITH THE THROTTLE CLOSED. NO ENG MALFUNCTION WAS FOUND ALTHOUGH THE ACFT WAS OUT OF ANNUAL.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC82FHD10
- Event ID
- 20020917X02557
- Case number
- NYC82FHD10
- 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: 2fc9a3a30da3c7cfc70a0f4d8b58e5384564303b340c7aaebdd2e7ad802261c9; retrieved 2026-09-24T03:20:26.432Z.