NTSB CAROL · Event
Event NYC98LA134
Registry · N6640H
FAA Aircraft Registry record.
Make / Model
CESSNA 172M
Year of manufacture
1975 · 23 years old at event
Engine
LYCOMING 0-320 SERIES (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19750626
ADS-B equipped
Yes — Mode-S A8C575
Registrant of record
SOLIS AVIATION LLC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's misjudgment of distance and speed during the approach/landing, and his delay in initiating a go-around. The quartering tailwind was a related factor.
Factual narrative
On June 24, 1998, at 1330 eastern daylight time, a Cessna 172, N6640H, owned and operated by Congressional Air Charter Inc., was substantially damaged while landing at Clearview Airpark Airport (2W2), Westminster, Maryland. The student pilot was not injured. Visual meteorological conditions prevailed for the instructional flight that originated at Frederick Municipal Airport (FDK), about 1300, destined for Montgomery County Airpark Airport (GAI), Gaithersburg, Maryland. No flight plan had been filed for the flight conducted under 14 CFR Part 91. In a written statement, the student pilot stated he had been doing traffic pattern work at FDK before attempting a return to GAI, the airplane's home base. While en route he became disorientated, and requested assistance from Baltimore Approach Control. Baltimore then provided him with radar vectors to 2W2. The pilot added that it was "quite windy and bumpy" as he entered the traffic pattern for 2W2. After touching down, the pilot realized that 2W2 was a "short field" and that he was not configured for that type of landing. He attempted to abort the landing, but during the maneuver, the airplane nosed over and came to rest inverted. A review of aeronautical information for GAI, FDK, and 2W2 showed the following. GAI: the airport where the airplane was based had one runway that was 4,201 feet in length, and 75 feet wide. FDK: the airport the student pilot was practicing traffic patterns at also had one runway measuring 5,220 feet in length, and 100 feet in width. 2W2, the accident airport had one runway measuring 1,845 feet in length, and was 30 feet wide. While returning to his home base, the student pilot became disorientated, and requested assistance from Baltimore Approach Control. Baltimore provided the pilot with radar vectors to an airport. He landed on runway 13 with a wind from 270 degrees at 12 knots. After touching down, the pilot realized that airport was a short field, and that he was not configured for that type of landing. He attempted a go-around, but could not get the airplane to lift off. Subsequently, it nosed over and came to rest inverted. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_NYC98LA134.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 (icing, 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 2019 · Conference Paper
Crash Testing and Simulation of a Cessna 172 Aircraft: Pitch Down Impact Onto Soft Soil
During the summer of 2015, NASA Langley Research Center conducted three full-scale crash tests of Cessna 172 (C-172) aircraft at the NASA Langley Landing and Impact Research (LandIR) Facility.
- NASA NTRS 2019 · Technical Memorandum (TM)
Simulating the Impact Response of Three Full-Scale Crash Tests of Cessna 172 Aircraft
During the summer of 2015, a series of three full-scale crash tests were performed at the Landing and Impact Research Facility located at NASA Langley Research Center of Cessna 172 aircraft.
- NASA NTRS 2026 · Contractor Report (CR)
Icing Physics Studies Using the 3D SIDRM Test Article: 2023 Icing Tests Analysis
In-flight icing is an important safety issue and is a factor that affects aircraft design and performance. Newer regulations are driving a need for improvements in airframe and engine icing simulation…
- arXiv 2025 · arXiv preprint
Multi-Agent Deep Reinforcement Learning for UAV-Assisted 5G Network Slicing: A Comparative Study of MAPPO, MADDPG, and MADQN
The growing demand for robust, scalable wireless networks in the 5G-and-beyond era has led to the deployment of Unmanned Aerial Vehicles (UAVs) as mobile base stations to enhance coverage in dense urb…
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Mathematical Model on the Temporal Dynamics of Aviation Competitive Pricing
This study investigates the competitive dynamics of airport pricing using U.S. airport data to validate the findings. It employs linear and nonlinear ordinary differential equation models to analyze t…
- 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.
Browse the full corpus — academia portal ↗