IAD97IA045
1997-01-25 · PROVINCETOWN, Massachusetts, United States · None · 1 aircraft · Status: Completed
Airport PVC
Aircraft involved
Probable cause & findings
the pilot's inadequate inflight planning/decision, and his misjudgment of speed and distance. Related factors were: fog, tailwind, and soft terrain on the overrun area at the end of the runway.
Factual narrative
On January 25, 1997, at 1400 eastern standard time, a Cessna 402C, N121PB, registered to Hyannis Air Service Inc., of Hyannis, Massachusetts, doing business as Cape Air 1088, sustained minor damage when it overran the runway during landing at the Provincetown Airport, Provincetown, Massachusetts. Instrument meteorological conditions prevailed, and an IFR flight plan had been filed. The certificated airline transport pilot and four passengers were not injured. The scheduled commuter flight was conducted under 14 CFR Part 135, and originated in Boston, Massachusetts, at 1330. The pilot reported that he checked the destination weather twice, once before departure, and the second prior to commencing the ILS 7 approach. He executed the approach, and made a normal touchdown. During the rollout, he experienced a strong, sudden, quartering tailwind, with wind gusts of approximately 20 knots. He said: "...The gust of wind carried the airplane down the runway instantaneously precluded a go-around and rendered braking ineffective. I employed maximum braking technique to bring the aircraft to a stop... ." The airplane then exited the runway onto the soft overrun area, and the right main gear collapsed. One of the passengers said, "...[when] the airplane touched down it seemed to veer a bit from side to side. It didn't slow down, and suddenly we were out of runway... ." The witness said it was very foggy. The pilot said he acquired the runway at approximately 250 feet AGL. He said the runway was wet, and there was patchy standing water. The weather briefing the pilot received prior to commencing the approach stated the winds were from 220 degrees at 12 knots. He said he was within the aircraft limitations, and the Automated Weather Observing System (AWOS) reports showed the winds began to gust after his normal approach and touchdown. The pilot stated there was no mechanical malfunction with the airplane. A Federal Aviation Administration Inspector reported that the airplane had touched down about 700 feet down the 3,498 foot long runway. The decision height for the ILS was 208 feet AGL. The Provincetown 1355 AWOS, reported winds from 220 degrees at 15 knots; visibility, 1/2 mile in fog; ceiling, 100 feet; temperature,43 degrees Fahrenheit (F); dewpoint, 43 F; and altimeter, 29.67 Hg. Five days after the accident, the airline issued parameters for arrivals and departures from the airport, which included landing with a maximum tailwind of 10 knots. The pilot reported that during an ILS Runway 7 Approach, he acquired the runway at 250 feet above the ground level, and performed a normal touchdown. After touchdown, the airplane continued down the 3,500 foot runway, and went off the end onto a soft overrun area, where the right main gear collapsed. The published decision height for the ILS approach was 208 feet. The 1335 EDT weather at the airport was reported, in part, to be 100 foot overcast, visibility 1/2 mile with fog, wind from 220 degrees at 15 knots. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_IAD97IA045.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Search this event elsewhere
External sources are reported, not agency: signal that something happened, not fact about what happened.
- TallyAero Live Wire Aviation press
- NTSB CAROL Agency ↗
- NTSB Docket Agency ↗
- Aviation Safety Network Aviation press ↗
- Kathryn's Report Aviation press ↗
- Aviation Herald Aviation press ↗
- AVweb Aviation press ↗
- Pilots of America Community ↗
- Reddit /r/flying Community ↗
- FlightAware Aviation press ↗
- AOPA accident database Aviation press ↗
- Google News News ↗
- DuckDuckGo News ↗
Related research
Matched on aircraft type or causal vocabulary (go-around). All research papers
- 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…