FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC89LA174 · Piper PA-28-161

24 Jul 1989 · Stonington, CT, United States

Piper PA-28-161 · Accident: in flight encounter with weather during initial climb

From Westerly, RI to Hartford Brainard Airport (HFD)

Report a problem

Event

NTSB case
NYC89LA174
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
Unknown

Piper PA-28-161

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
N29216
Onboard fatalities
Unknown
Route
From Westerly, RITo Hartford Brainard Airport (HFD), Hartford, 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
Initial climb
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 encounter with weather
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Visual flight rules (VFR) flight into instrument meteorological conditions (IMC); Tree(s)
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Pilot in command › Aircraft control, not maintained
  • Pilot in command › Spatial disorientation
  • Pilot in command › VFR flight into imc, inadvertent

Approximate · Estimated position: the centre of Stonington, CT, the place the record names. Not the accident site.

NTSB narrative

BEFORE TAKEOFF, THE PLT OBTAINED WX INFO. NO WX RPRT WAS AVAILABLE FOR THE DEP ARPT, BUT THE DESTN (HARTFORD, CT) WAS RPRTD AS CLEAR. THE PLT SAID HE WAS INFORMED ON UNICOM FREQ THAT THERE WAS ONLY GROUND FOG IN RHODE ISLAND, WHICH SHOULDNOT HAVE INTERFERED WITH HIS FLT TO HARTFORD. AFTER PREFLIGHTING THE ACFT, HE 'OBSERVED THE STARS DIRECTLY OVERHEAD AND CONCLUDED THAT THERE WAS JUST GROUND FOG.' ALSO, THE PLT STATED THAT AFTER TAKEOFF, THE ACFT HAD CLIMBED TO 200 FT MSL WHEN HE SUDDENLY REALIZED THE DENSITY OF THE FOG WAS THICKER THAN RPRTD OR ANTICIPATED. (THE ARPT ELEV WAS 81 FT.) HE SAID HE THEN EXPERIENCED VERTIGO (SPATIAL DISORIENTATION) & LOST CONTROL OF THE ACFT. SUBSEQUENTLY, THE ACFT HIT THE TOPS OF TREES & CRASHED IN THE PAWCATUCK RIVER. AS THE ACFT SANK, THE OCCUPANTS EGRESSED, THEN SWAM TO A DOCK WHERE THEY RCVD HELP.

Probable cause

THE PILOT'S INADVERTENT FLIGHT INTO INSTRUMENT METEOROLOGICAL CONDITIONS (IMC) AND HIS LOSS OF AIRCRAFT CONTROL DUE TO SPATIAL DISORIENTATION. FACTORS RELATED TO THE ACCIDENT WERE: THE ENVIRONMENTAL CONDITIONS (DARK NIGHT & FOG) AND THE PILOT'S LACK OF INSTRUMENT EXPERIENCE.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC89LA174
Event ID
20001213X28968
Case number
NYC89LA174
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1989-07-25.
  • API snapshot SHA-256: 738cb6df41916d46960749a3c311c93babf4db3a8aa1ee0a375da786aa288ab5; retrieved 2026-09-21T15:52:23.672Z.