Piper PA-23-250 accident near Thirkleby, Uk, June 29, 2006
On June 29, 2006 at about 12:37 pm local time, a Piper PA-23-250, registered GBBEY, was destroyed in an accident near Thirkleby. It was a flight of an unrecorded kind under non-U.S. private rules. 1 person was killed.
The NTSB's probable cause their words, unchanged
The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- June 29, 2006 · about 12:37 pm local time
- Place
- Thirkleby, United Kingdom
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- not recorded
- Aircraft
- Piper PA-23-250 · all PA-23-250s on the register
- Registration
- GBBEY · no longer on the register
- Damage
- Destroyed
- Flight
- Flight of an unrecorded kind · non-U.S. private rules
The factual record from the NTSB's investigation tables, in plain English
The aircraft
- Landing gear: fixed
Weather at the time
- Temperature: 0°F (-18°C), dew point 0°F (-18°C)
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
