NTSB CAROL · Event
Event NYC98LA029
Registry · N7027N
FAA Aircraft Registry record.
Make / Model
POWRACHUTE PEGASUS
Year of manufacture
2003
Engine
ROTAX 582SER (65 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
20091120
ADS-B equipped
Yes — Mode-S A95F56
Registrant of record
BRYANT BRUCE E
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's improper in-flight planning/decision, his misjudgment of speed and distance while on final approach to land, and his delay in aborting the landing after failing to attain a proper touchdown point for landing.
Factual narrative
On November 19, 1997, at 1355 eastern standard time, a Beech E33A, N7027N, was substantially damaged when it collided with trees during an aborted landing at the Clearview Airpark, Westminister, Maryland. The certificated commercial pilot received serious injuries. Visual meteorological conditions prevailed for the personal flight that originated at Hagerstown, Maryland, about 1330. No flight plan had been filed for the flight conducted under 14 CFR Part 91. According to a witness, the airplane touchdown "pretty fast" on runway 18, about mid-field. The witness also stated: "...He was landing downwind with about 8 to 10 knots of wind...He touched down fast enough to smoke the tires when he applied the brakes. Then he added power to initiate a go-around about 200 feet from the end of the runway as the black marks substantiate. The airplane disappeared behind the hill..." The witness also stated that his wife landed an airplane about 20 minutes after the accident, and she estimated the winds were 10 knots, gusting to 20. During an interview with a Federal Aviation Administration (FAA) Inspector, the pilot was asked why he landed on runway 13, when the wind favored runway 31, to which the pilot responded, "It's normal to land uphill." In the NTSB Form 6120.1/2, the pilot stated that he did not have any recollection of the accident. According to the FAA Inspector, the terrain beyond the departure end of runway 13 sloped down. The tops of trees, about 450 feet from the departure end of the runway, were just above the runway elevation. The airplane struck the tops of the trees and then impacted the ground. The FAA Inspector observed about 250 feet of tire rubber marks on the runway beyond the point where the airplane touched down. The asphalt runway was 1,845 feet long and 30 feet wide. The Inspector's examination of the airplane revealed continuity from the pilot's flight controls to the airplane's control surfaces. The winds at an airport 8 miles north of Clearview were reported to be from 280 degrees at 8 knots, gusting to 20. The winds at Baltimore, Maryland, 24 miles southeast of Clearview, were reported to be from 280 degrees at 10 knots, gusting to 17. The pilot flew his airplane on a 30 minute flight from one airport to another. A witness observed the airplane touch down 'fast' about mid-field, on the 1,845 foot long runway. The engine was heard to power up when the airplane was about 200 feet from the departure end of the runway. The airplane then struck trees about 450 feet beyond the end of the runway. Winds at the airport were estimated to be from the northwest at 10 gusting 20 knots. The terrain at the departure end of the runway sloped down, and the tree tops were at the runway elevation. The pilot did not recall the accident; however, when asked why he landed downwind on runway 13, he stated, 'It's normal to land uphill.' Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1997_NYC98LA029.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 (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 ↗