NYC86LA085 · Rockwell 680FL
Rockwell 680FL · Accident: on ground/water encounter with weather during landing
From Bangor International Airport (BGR) to William P. Hobby Airport (HOU)
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
- NYC86LA085
- 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
- Charter & commuter
- 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
Rockwell 680FL
- Aircraft type
- Rockwell 680
- 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
- N287B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Bangor International Airport (BGR), Bangor, METo William P. Hobby Airport (HOU)
- 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 135: Air Taxi & Commuter
- 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 encounter with weather
- 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 › Planning/decision, improper
Approximate · Estimated position: the centre of Houlton, ME, the place the record names. Not the accident site.
NTSB narrative
THE PILOT-IN-COMMAND LANDED ON RUNWAY 5 WHICH HAD APPROXIMATELY 1 INCH OF FRESH SNOW. HE REPORTED THAT HE ENCOUNTERED WHITEOUT CONDITIONS DURING THE LANDING & LOST REFERENCE TO THE RUNWAY CENTERLINE. THE AIRCRAFT TOUCHED DOWN ON THE LEFT SIDE OF THE RUNWAY, ANGLED OFF THE LANDING AREA IN A STRAIGHT LINE & COLLIDED WITH A SNOWBANK. AT THE TIME OF THE ACDNT, THERE WAS LIGHT FREEZING DRIZZLE, ICE PELLETS & FOG. THE LOCAL FSS WAS CLOSED & THERE WAS NO CURRENT WX INFO AVAILABLE TO THE PLT FOR THE DESTN ARPT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC86LA085
- Event ID
- 20001213X33164
- Case number
- NYC86LA085
- 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: 38aec50211b1b2bd0f47792d50dc0bd9ee82dce9506a87e73f7266559269dcf4; retrieved 2026-09-18T20:04:03.185Z.