NYC95LA111 · Rockwell 112B
Rockwell 112B · Accident: loss of control on ground/water during landing
From CKP · CHESAPEAKE, MD to Lee Airport (ANP)
Event
- NTSB case
- NYC95LA111
- 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
Rockwell 112B
- Aircraft type
- Rockwell 112
- 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
- N1409J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From CKP · CHESAPEAKE, MDTo Lee Airport (ANP)
- 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
- Loss of control on ground/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 › Flight into adverse weather, continued
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE AIRPLANE LANDED ON A WET, NARROW 2500-FT RUNWAY. WHEN THE PILOT APPLIED THE BRAKES, THE AIRPLANE SKIDDED, DEPARTED THE RUNWAY, AND STRUCK A FENCE AND POLE. ACCORDING TO THE PILOT HE IMMEDIATELY APPLIED 'FULL BRAKES...BUT THERE WAS NIL SENSATION OF BRAKING EFFECT.' WITNESSES SAID IT WAS RAINING HEAVY, AND THE WINDS WERE GUSTING AND CHANGING DIRECTION. A WITNESS SAID THERE WERE 'STRONG GUSTING WINDS THAT WOULD BE A TAILWIND FOR LANDING ON RUNWAY 12.' ANOTHER WITNESS SAW THE AIRPLANE ON FINAL, AND '...IT WAS LINED UP FOR RUNWAY 12, APPEARED TO BE HIGH ON THE APPROACH AND FAST...[AND] APPEARED TO BE IN A CRAB....' THE NEAREST REPORTED WEATHER WAS AT BALTIMORE, ABOUT 14 NM NORTH OF THE ACCIDENT SITE. THE 1805 OBSERVATION WAS 1,700 BROKEN, 12,000 OVERCAST, VISIBILITY 7 MILES, THUNDERSTORMS AND LIGHT RAIN, WIND 260 DEG AT 9 KNOTS, GUSTING TO 21.
Probable cause
THE PILOT'S IMPROPER DECISION TO CONTINUE HIS FLIGHT INTO THE ADVERSE WEATHER CONDITIONS THAT EXISTED AT THE DESTINATION AIRPORT. THE WEATHER CONTRIBUTED TO THE ACCIDENT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC95LA111
- Event ID
- 20001207X03535
- Case number
- NYC95LA111
- 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: 691cdc309f761df37fd623b995450c86d3e60b53a6960acb920c648cf5514069; retrieved 2026-09-22T23:57:17.877Z.