FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC06FA155 · Piper PA-34-220T

25 Jun 2006 · Tafton, PA, United States

Piper PA-34-220T · Accident: loss of control in flight en route

From Piedmont Triad International Airport (GSO) to Sanford Seacoast Regional Airport (SFM)

Report a problem

Event

NTSB case
NYC06FA155
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
3 · 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

Piper PA-34-220T

Aircraft type
Piper PA-34
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
N8371X
Operator
Walter M. Daggett · private individual
Onboard fatalities
Unknown
Route
From Piedmont Triad International Airport (GSO), Greensboro, NCTo Sanford Seacoast Regional Airport (SFM), Sanford, ME
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
En route · cruise
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 in flight
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 › Flight into adverse weather, inadvertent

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

About an hour before takeoff, the pilot obtained an updated weather briefing, which included a discussion about thunderstorm activity along the route of the flight. About 2 hours 30 minutes after takeoff, the pilot was deviating around thunderstorm activity when the airplane disappeared from radar. A witness near the accident heard the engine "revving up and down," a "muffled pop," and then silence, before seeing debris falling from the sky, well above the tree line. Examination of the airplane revealed that it experienced an in-flight breakup; however, no evidence of a mechanical malfunction was identified. Weather radar images indicated the airplane entered a developing area of moderate to heavy intensity echoes consistent with a convective cell or thunderstorm. The pilot advised air traffic control he was receiving weather information through a portable GPS receiver, with a weather subscription service. There were no published Convective SIGMETs (significant meteorological information), SIGMETs, or Center Weather Advisories for thunderstorms, current at the time of the accident for the area encompassing the accident site. The pilot received his airplane multiengine rating, on May 13, 2006, as of as of June 18, 2006, the pilot had accumulated about 1,720 hours of total flight experience, which included 32.6 hours in multiengine airplanes; of which 26.8 hours were accumulated in the accident airplane. In addition, the pilot had logged about 140 and 68 hours of actual and simulated instrument flight experience; respectively. Except for 0.4 hours of simulated instrument flight experience logged during his multiengine rating check ride; the pilot had not logged any additional instrument flight experience in multiengine airplanes.

Probable cause

The pilot's inadvertent encounter with a thunderstorm, which resulted in a loss of aircraft control, and a subsequent in-flight breakup.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC06FA155
Event ID
20060712X00926
Case number
NYC06FA155
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: 769baf81b51ae129af52dff500c502fd3606cb863cd04b887e48a97a8baa65c0; retrieved 2026-09-20T17:15:35.910Z.