Skip to content

Atlas / NTSB / BFO94LA148

NTSB CAROL · Event

Event BFO94LA148

1994-08-25 SKOWHEGAN, Maine, United States Airport · OWK None 1 aircraft Status: Completed

Registry · N11HK

FAA Aircraft Registry record.

Make / Model

PIPER PA-32R-301T

Year of manufacture

1981 · 13 years old at event

Engine

AMA/EXPR UNKNOWN ENG

Seats / Engines

7 seats · 1 engine

Last airworthiness date

19810424

ADS-B equipped

Yes — Mode-S A02A93

Registrant of record

JOHNSON WENDELL F

Source: FAA Aircraft Registry (releasable master file).

Aircraft involved

Probable cause & findings

The pilot's failure to do a go around which resulted in an inflight collision with trees during a delayed aborted landing to avoid a runway overrun.

Factual narrative

On August 25, 1994, at 0635 eastern daylight time, N11HK, a Piper PA 28-181, owned and operated by Paul D. Spiro of Abington, Massachusetts, collided with trees during takeoff at Central Maine Airport of Norridgewock, Maine. The certificated private pilot, the sole occupant, was not injured and the airplane sustained substantial damage. Visual meteorological conditions prevailed and a flight plan was not filed. The business flight was operated under 14 CFR 91 and had originated in Norwood, Massachusetts. According to the pilot, he was going to Maine to pick up a patient and take him to Boston, Massachusetts, for treatment. The pilot, a volunteer airlife pilot stated that he overflew the field and selected runway 3 for the landing as that runway was clear of fog. He stated that as the airplane was about 30 to 50 feet above the approach end of the runway, he lost sight of the runway due to the ground fog. The pilot stated that he increased the power to go-around, but as he started his go-around the runway came into sight again, so he decided to land. The pilot stated that during the landing, he realized that there was not enough runway remaining so he tried to go around again. During the climb out at about 20 feet above the ground, the airplane struck trees at the departure end and fell to the ground. The pilot reported that there was no mechanical malfunction. THE VOLUNTEER, AIRLIFE PILOT STATED THAT HE RECEIVED A WEATHER BRIEFING. HE STATED THAT UPON ARRIVAL AT HIS DESTINATION HE OVERFLEW THE AIRPORT AND HE SELECTED RUNWAY 3 AS THERE WAS SOME FOG IN THE AREA, BUT RUNWAY 3 WAS CLEAR OF FOG. THE PILOT REPORTED THAT ON FINAL APPROACH AS HE PASSED OVER THE APPROACH END OF RUNWAY 3 AT APPROXIMATELY 30 TO 50 FEET ABOVE THE RUNWAY, HE LOST SIGHT OF THE RUNWAY ENVIRONMENT. THE PILOT STATED THAT HE INCREASED THE POWER TO GO-AROUND, BUT AS HE STARTED HIS GO-AROUND THE RUNWAY CAME INTO SIGHT AGAIN, SO HE DECIDED TO LAND. THE PILOT STATED THAT DURING THE LANDING, HE REALIZED THAT THERE WAS NOT ENOUGH RUNWAY REMAINING SO HE TRIED TO GO-AROUND AGAIN. DURING THE CLIMB OUT AT ABOUT 20 FEET ABOVE THE GROUND, THE AIRPLANE STRUCK TREES AT THE DEPARTURE END AND FELL TO THE GROUND. THE PILOT REPORTED THAT THERE WAS NO MECHANICAL MALFUNCTION. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12

Verbatim from NTSB's published report. Source file NTSB_1994_BFO94LA148.txt. Findings + structured fields enriched from FAA avall.mdb. Full investigation docket on data.ntsb.gov ↗.

Related research

What the literature says.

Academic papers and agency reports matching this event's aircraft type or causal vocabulary (go-around). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.

Browse the full corpus — academia portal ↗