NTSB CAROL · Event
Event ANC08LA018
Aircraft involved
Probable cause & findings
The flight instructor's inadequate supervision of the student, and his delayed go-around. Contributing to the accident was dark night conditions.
Factual narrative
On November 9, 2007, about 1823 Alaska standard time, a Cessna 150 airplane, N11764, sustained substantial damage when it collided with trees and grass-covered terrain while on approach to runway 34, at the Palmer Municipal Airport, Palmer, Alaska. The airplane was being operated by Pegasus Aviation, Palmer, as a visual flight rules (VFR) instructional flight under Title 14, CFR Part 91, when the accident occurred. The certificated flight instructor (CFI) and the student pilot received serious injuries. Dark night visual meteorological conditions prevailed, and no flight plan was filed. The airplane departed the Wolf Lake Airport, Palmer, Alaska, about 1815. A Federal Aviation Administration (FAA) airworthiness inspector from the Anchorage Flight Standards District Office responded to the accident scene shortly after the accident, and examined the airplane prior to recovery efforts. The FAA inspector reported that rescue personnel told him they talked to the student pilot shortly after the accident, and before he was transported to the hospital. They said the student pilot told them that the airplane struck a stand of trees at the approach end of runway 34, while he was receiving dual instruction during dark night conditions. The airplane came to rest inverted, about 300 yards short of the approach end of runway 34. It sustained substantial damage to the wings, fuselage, and empennage. The FAA airworthiness inspector reported that during his postaccident inspection of the airplane, no preaccident mechanical anomalies with the airplane were discovered. The CFI did not complete an NTSB Pilot/Operator Aircraft Accident Report (NTSB Form 6120.1). In a written statement to the FAA, dated January 24, the CFI reported that while on final approach to runway 34, he inadvertently allowed the student pilot to descend too steeply, and with higher than normal airspeed. He said his verbal command for the student to arrest the descent and slow the airplane's airspeed was initially followed, but the student pilot again allowed the airplane to attain a rapid descent rate and high airspeed as the approach continued. The CFI said that he then took control of the airplane, added full engine power, and initiated a go-around. During the attempted go-around, the CFI said he encountered a severe windshear. He wrote, in part: "I felt the aircraft had gotten into a severe vertical wind shear, and no amount of power we had available was stopping the rate of descent, and we hit the ground." The closest weather observation station is the Palmer Municipal Airport. On November 9, at 1753, an Aviation Routine Weather Report (METAR) was reporting in part: Sky conditions and ceiling, 8,500 feet broken; visibility, 10 statute miles; wind, 350 degrees (true) at 9 knots. The certificated flight instructor (CFI) was providing flight instruction to a student pilot. While on a northerly approach to the runway, during dark night conditions, the CFI said he inadvertently allowed the student pilot to descend too steeply, and with a high airspeed. His verbal command for the student to stop the excessive descent and slow the airspeed was initially followed, but the student pilot again allowed the airplane to attain a rapid descent rate and high airspeed as the approach continued. The CFI took control of the airplane, added full engine power, and initiated a go-around. During the attempted go-around, the CFI said he encountered severe windshear. He wrote, in part: "I felt the aircraft had gotten into a severe vertical windshear, and no amount of power we had available was stopping the rate of descent, and we hit the ground." The airplane collided with a stand of trees and came to rest inverted, about 300 yards short of the approach end of the runway, sustaining substantial damage to the wings, fuselage, and empennage. At the time of the accident wind conditions were reported to be 350 degrees (true) at 9 knots. An FAA airworthiness inspector reported that during his postaccident inspection of the airplane, no preaccident mechanical anomalies with the airplane were discovered. Due to the absence of any mechanical problems with the airplane, the dark night conditions, and the relatively light winds reported at the time of the accident, it is probable that the accident could have been prevented if the CFI had provided better supervision of the student and initiated a go-around sooner. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2007_ANC08LA018.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (wind shear, 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.
- NASA NTRS 2025 · Conference Paper
A Training Study to Improve Monitoring During A Go-Around
As part of an FAA program to improve go-around (GA) safety, we were asked to determine if we could improve the performance of the Pilot Monitoring (PM) during a GA maneuver.
- Flight Safety Foundation 2024 · FSF / AeroSafety World
Go-Around Safety Forum Findings
Foundation Go-Around Safety Forum technical findings — examines why pilots fail to execute go-arounds when criteria are met (stabilized approach gate not met, energy state out of envelope, traffic con…
- Semantic Scholar 2022 · Article (Journal of Safety Research)
Go-around accidents and general aviation safety.
INTRODUCTION Changes in General Aviation (GA) accident rates, specifically in the go-around phase, are examined by comparing the number of accidents, the proportion of fatal accidents, and the proport…
- Semantic Scholar 2021 · Article (Aerospace)
Classification and Analysis of Go-Arounds in Commercial Aviation Using ADS-B Data
Go-arounds are a necessary aspect of commercial aviation and are conducted after a landing attempt has been aborted. It is necessary to conduct go-arounds in the safest possible manner, as go-arounds …
- NASA NTRS 2021 · Accepted Manuscript (Version with final changes)
Go-Around Criteria Refinement for Transport Category Aircraft
Presently, airline pilots are trained to go around if, when lower than 500 ft above the ground, they are outside of a handful of parameters such as airspeed, position, and rate of descent.
- NASA NTRS 2019 · Conference Paper
Validation of Proposed Go-Around Criteria Under Various Environmental Conditions
This paper evaluates the effects of environmental conditions on touchdown performance under varying approach states and validates proposed go-around criteria developed using data from a previously con…
Browse the full corpus — academia portal ↗