IAD02FA024 · Piper PA-28R-180
Piper PA-28R-180 · Accident: in flight collision with terrain/water on approach
From Burke Lakefront Airport (BKL) to Igor I Sikorsky Memorial Airport (BDR)
Event
- NTSB case
- IAD02FA024
- 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
- 1 · 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
- Visual Meteorological Cond
Piper PA-28R-180
- Aircraft type
- Piper PA-28
- 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
- N7427J
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Burke Lakefront Airport (BKL), Cleveland, OHTo 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
- Approach · IFR final approach
- 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 › IFR procedure, not followed
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot departed on a night cross-country flight, with the destination airport located on the northern coast of Long Island Sound. He arrived from the northwest, but could not locate the airport. After several conversations with the tower controller, he was switched to approach control, and subsequently issued a clearance for the VOR Runway 29 approach. The pilot's last transmission was that he was abeam the final approach fix. Radar data indicated that the airplane proceeded off the coast about 8 miles east of the airport before initiating a gradual, descending right turn back towards the airport. During the last 2 minutes, the airplane was on a general heading of 300 degrees, descending about 1,300 feet per minute. The last radar contact, when the airplane was 200 feet above the water, was about 350 degrees magnetic, 3/4 nautical mile from the final approach fix. The final approach course was 275 degrees, and included a decision altitude of 380 feet. The frequency dialed into the airplane's VOR receiver was the same as the VOR. The night meteorological conditions included clear skies, a visibility of 10 statute miles, and a moon illumination of 99 per cent. Another pilot who was flying in the area at the same time reported that the moon and the city lights were "bright" at the time of the accident, and the airport runway lights were easily identifiable. Examination of the airplane revealed no mechanical anomalies.
Probable cause
The pilot's failure to follow the published IFR approach procedure, which resulted in a premature descent and subsequent impact with water. A factor was the night, overwater visual conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record IAD02FA024
- Event ID
- 20020110X00057
- Case number
- IAD02FA024
- 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, coordinates. 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: 4d142df012e935f17afba1ee768833460a264e448ac1aee58467616a071d8613; retrieved 2026-09-20T20:15:23.115Z.