# Accident 20070622016049A: Piper PA30, Highgate, VT, June 22, 2007

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 22, 2007, 10:15 local time
- Place: Highgate, VT
- Airport: Franklin County State
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 44.9833° N, 73.1667° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=44.9833&lon=-73.1667&mi=10
- Aircraft: N8078Y, a cancelled registration (https://openairdocs.org/deregistered/N8078Y-2013-05-13) (OpenAirDocs)
- Registry model: Piper PA-30 (registry code 7103002, https://openairdocs.org/model/piper-pa-30) (OpenAirDocs)
- Registry engine: Lycoming IO-320 series (registry code 41509, https://openairdocs.org/engine/lycoming-io-320-series) (OpenAirDocs)
- Reported make and model: PIPER PA30
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 3,530 total, 900 in this make and model, 8 in the last 90 days
- NTSB investigation: [NTSB DEN07CA103](https://openairdocs.org/ntsb/DEN07CA103) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20070622016049A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) PILOT IN COMMAND DEPARTED THE SOUTH ALBANY NEW YORK AIRPORT (4BO) AT APPROXIMATELY 09:10 AM ON JUNE 22, 2007, ENROUTE TO THE FRANKLIN COUNTY STATE AIRPORT (FSO). AT APPROXIMATELY 10:15 AM THE PILOT IN COMMAND STATED THAT HE BEGAN A STRAIGHT IN APPROACH TO RUNWAY 1 (ASPHALT 3000' X 60"). PIC FURTHER STATED THAT WINDS WERE INDICATING 340 DEGREES AT APPROXIMATELY 8 KNOTS. PILOT ALSO STATED THAT THERE WAS A CEILING AT ABOUT 2500' TO 3000.' PHOTOGRAPHS SHOW THAT THE MAIN LANDING WHEELS STRUCK THE TURF ABOUT 30 FEET PRIOR TO THE BEGINNING OF RUNWAY 1. THERE IS A NOTICEABLE "BERM" OF TURF JUST BEFORE THE ASPHALT BEGINS. IT APPEARS THAT THIS MADE THE AIRCRAFT GO BACK AIRBORNE. THERE WERE NO PROPELLER STRIKE MARKS ON THE RUNWAY PAVEMENT NOR ANY OTHER SIGNS OF SCRAPES OR GOUGES ON THE RUNWAY. JUST A SHORT DISTANCE FROM THE BEGINNING OF RUNWAY 1, PHOTOGRAPHS SHOW THAT THE UNDERCARRIAGE OF THE AIRCRAFT MADE CONTACT WITH THE TURF THAT BORDERS THE RUNWAY. THIS WOULD BE ON THE LEFT (WEST SIDE) OF THE RUNWAY. AFTER THE AIRCRAFT CONTACTED THE TURF, IT'S FINAL RESTING POINT WAS THAT THE NOSE OF THE AIRCRAFT WAS FACING TO THE WEST SOUTHWEST. MOST OF THE DAMAGE WAS DONE WHEN THE AIRCRAFT MADE CONTACT WITH THE TURF ON THE SECOND CONTACT.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB DEN07CA103](https://openairdocs.org/ntsb/DEN07CA103), Jun 22, 2007: Piper PA-30 (N8078Y), Highgate, VT, substantial damage. Probable cause: The pilot's failure to maintain airspeed on approach resulting in the stall and subsequent impact with terrain.

## Other reports on N8078Y (2)

Matched to the same aircraft by N-number and date.

- [Incident 19811201083719I](https://openairdocs.org/incident/19811201083719I), Dec 1, 1981: Piper PA30 (N8078Y), Bedford, MA, Minor damage. Failed to lower landing gear for landing. Landed gear up.
- [Incident 19780831038379I](https://openairdocs.org/incident/19780831038379I), Aug 31, 1978: Piper PA30 (N8078Y), Great Barringto, MA. Pilot did not hold as instructed, but shot an approach without clearance from ATC.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.