NYC01FA084 · Hawker Siddeley HS-125-3A
Hawker Siddeley HS-125-3A · Accident: overrun during landing
From Bradley International Airport (BDL) to Igor I Sikorsky Memorial Airport (BDR)
Event
- NTSB case
- NYC01FA084
- 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
- Instrument Meteorological Cond
Hawker Siddeley HS-125-3A
- Aircraft type
- Hawker Siddeley HS-125
- 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
- N48DD
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Bradley International Airport (BDL), Windsor Locks, CTTo Igor I Sikorsky Memorial Airport (BDR), Bridgeport, CT
- 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
- Overrun
- 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 › Preflight planning/preparation, inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Arriving in the Bridgeport Airport area, the Pilot-in-Command (PIC) received the ATIS, which stated that the visibility was 1/2-mile with snow and fog. The ILS Runway 06 approach was in use. Braking action advisories were in effect, and all surfaces were covered with thin wet snow. During the approach to the airport, with the Second-in-Command (SIC) at the controls, the PIC visually observed that the hydraulic pressure gauge, "smiley face," was normal, and he performed a "brake test." The tower controller advised the flightcrew that a Navajo had just landed and reported a 250-foot ceiling, 3/4 miles of visibility, and that the runway braking action was "good." On final approach, the airplane broke out of the overcast clouds about 400 feet above the ground. The runway appeared dry, with only blowing snow across it. As the airplane touched down about 1,463 feet beyond the approach end of the 4,677-foot long runway on the runway, the SIC stated that she did not have any braking effectiveness, and selected the "dump flaps" to slow the airplane. The airplane continued down the runway and did not seem to be slowing to a safe speed. The flightcrew observed the 1,000-foot marker approaching and the SIC selected the emergency brakes. After she felt a lack of deceleration, the SIC selected the parking brake. The airplane continued off the end of the runway, impacted a non-frangible fence, and came to rest with about 4 feet of the airplane protruding onto a public access road. Examination of the airplane revealed a reference speed set on the pilot's airspeed indicator of 117 knots. According to the Hawker Siddeley HS-125 Airplane Flight Manual (AFM) performance section, the uncorrected landing distance, on a dry runway, at the estimated landing weight of the airplane was approximately 2,610 feet. The AFM performance section also had a chart for the "Effect of Slippery Runway on Landing Distance." The chart determined that the "equivalent scheduled landing distance available," was approximately 2,150 feet. According to airport records, a NOTAM was issued the day of the accident, which referenced the condition of the runway surfaces as having "Thin wet snow all surfaces." An air traffic controller observed slush "spraying" from the airplane, which extended 5 feet from the airplane, as the airplane rolled out. The airplane's braking system was tested after the accident and no abnormalities were noted.
Probable cause
The pilot-in-commands inadequate preflight planning resulting in an approach to a runway with insufficient length. A factor related to the accident was the slush covered runway which resulted in a hydroplaning condition.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC01FA084
- Event ID
- 20010316X00592
- Case number
- NYC01FA084
- 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: a8c6713c5cf0e294cb39c2ba952ae70246c3c191f4b4a513ae613f747e689a8b; retrieved 2026-09-22T12:06:38.630Z.