NTSB CAROL · Event
Event SEA00FA127
Registry · N7625M
FAA Aircraft Registry record.
Make / Model
STODDARD HAMILTON GLASTAR GS-1
Year of manufacture
2008
Engine
LYCOMING HIO-360-B1A (180 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
20080827
ADS-B equipped
Yes — Mode-S AA4C09
Registrant of record
MCCOWAN KENNETH L
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
Failure to maintain clearance from mountainous/hilly terrain.
Factual narrative
On July 08, 2000, about 0840 Pacific daylight time, a Cessna 175, N7625M, was destroyed when it collided with mountainous terrain approximately 13 nautical miles southeast of Molalla, Oregon. The airplane was registered to and operated by the pilot as a visual flight rules (VFR) personal flight under the provisions of Title 14 CFR Part 91, when the accident occurred. The commercial pilot, the sole occupant of the airplane, was fatally injured. Visual meteorological conditions prevailed and no flight plan was filed for the cross-country flight. Impact forces and post-crash fire destroyed the airplane, and there was no report of ELT activation. The airplane departed Aurora, Oregon, at 0800. On the morning of July 8th, a group of about 16 people and 10 aircraft, including the pilot of the accident airplane, convened at Aurora State Airport (UAO). The gathering was a reoccurring event with participants from the local flying community. The participants planned on flying from Aurora to Salem, Oregon, for breakfast followed by a return flight to Aurora later that day. However, due to low ceilings (reported at 1,800 feet AGL), the group changed the intended destination from Salem to Lebanon, Oregon. Shortly after departing Aurora, the pilot of the accident airplane was contacted by another pilot (on 122.75 megahertz) who was participating in the fly-in. At that point, the pilot of the accident airplane indicated that he was underway. That was the last know communication to/from the accident airplane. On the evening of July 8th, after the pilot failed to return home from the morning flight, family members reported the overdue airplane to the Federal Aviation Administration in McMinnville, Oregon. McMinnville Flight Service Station (FSS) subsequently issued an ALNOT (alert notice) and search and rescue personnel were notified. The following day, approximately 2345, search and rescue personnel located the airplane wreckage.
PERSONNEL INFORMATION
The pilot held a commercial pilot certificate with single-engine land, multi-engine land and instrument airplane ratings. The pilot held a third-class medical certificate issued on September 2, 1998. The pilot's flight logbook indicated that he had accumulated approximately 1,572 hours in single-engine airplanes, 11 of which were accumulated in the 90 days preceding the accident. The logbook also indicated that the pilot had successfully completed a biennial flight review on June 16, 2000.
AIRCRAFT INFORMATION
The airplane was manufactured and certificated on February 12, 1959. It was powered by a Continental GO-300 series engine, rated at 175 horsepower. According to maintenance records, the airplane's last annual inspection was performed on December 11, 1999.
METEOROLOGICAL INFORMATION
The 0840 SPECI (Special) observation at Aurora, approximately 21 nautical northwest of the accident location, reported variable winds at 3 knots; visibility 10 statute miles; scattered clouds at 2,600 feet AGL; overcast clouds at 3,800 feet AGL; temperature 14 degrees C; dew point temperature 10 degrees C; altimeter setting 29.90 inches Hg. The 0853 SPECI observation at Aurora, reported winds from 190 degrees at 3 knots; visibility 10 statute miles; few clouds at 2,800 feet AGL; broken clouds at 3,400 feet AGL; broken clouds at 4,100 feet AGL; temperature 14 degrees C; dew point temperature 10 degrees C; altimeter setting 29.90 inches Hg. The 0926 SPECI observation at Aurora, reported winds from 330 degrees at 3 knots; visibility 10 statute miles; few clouds at 2,700 feet AGL; broken clouds at 4,800 feet AGL; broken clouds at 6,000 feet AGL; temperature 16 degrees C; dew point temperature 11 degrees C; altimeter setting 29.90 inches Hg.
WRECKAGE AND IMPACT INFORMATION
On July 10, 2000, investigators from the National Transportation Safety Board, Cessna Aircraft and the Federal Aviation Administration examined the airplane wreckage. The wreckage was located on private forested land at an elevation of approximately 2,826 feet above sea level. The airplane came to rest at 44 degrees, 59 minutes north latitude, and 122 degrees, 26 minutes west longitude. A grouping of large conifer trees (estimated to be 150 feet in height) with fresh scarring, approximately 80 feet above ground level, was observed approximately 470 feet southwest of the main wreckage. The magnetic bearing from the conifer trees to the main wreckage/burn area was approximately 035 degrees magnetic (wreckage diagram and photographs attached). All airplane components were located at the crash site. The main wreckage, consisting of the charred remains of the cabin area, empennage and engine were located on a service road at the northeast end of the wreckage distribution path. The cabin area, from the engine compartment to the rear bulkhead, was entirely destroyed by fire and impact forces. A section of the left wing and flap assembly was found lying next to the charred remains of the fuselage. The remaining section of left wing and associated aileron were found along the wreckage distribution track, approximately 370 feet southwest of the main wreckage. The airplanes right wing (which had separated at the wing root), lift strut, flap and aileron, were found, as a unit, approximately 310 feet southwest of the main wreckage. Rearward crushing was noted to the right horizontal stabilizer and elevator. The left side horizontal stabilizer and elevator had separated from the empennage and were found lying in the immediate area of the main wreckage. Minimal damage was noted to the vertical stabilizer and still attached rudder. The propeller assembly and reduction gear separated as a unit from the crankcase and were found approximately 222 feet southwest of the main wreckage. Forward span wise bending (toward the low pressure side of the propeller) was noted to propeller blade A. The last 6-7 inches of the blade was curled forward approximately 120 degrees. Span wise aft bending was noted to propeller blade B.
MEDICAL AND PATHOLOGICAL INFORMATION
An autopsy on the pilot was conducted by the Oregon State Medical Examiner's Office, Portland, Oregon, on July 10, 2000. According to the postmortem report, the pilot's cause of death was attributed to "blunt force trauma." The manner of death was listed as accidental. Toxicology testing on the pilot was conducted by the FAA Civil Aeromedical Institute (CAMI), Oklahoma, Oklahoma. According to the toxicology report, results were negative for Ethanol. An unspecified amount of Quinine was detected in the pilot's Liver.
ADDITIONAL INFORMATION
On July 10, 2000, the airplane wreckage was recovered by personnel from HLM Air Service, Inc, and transferred to their facility in Independence, Oregon. On July 18, 2000, representatives from Teledyne Continental Motors and the National Transportation Safety Board examined the airplane's engine. Extensive impact and thermal damage was noted to the frontal area, bottom area and accessory region of the engine assembly. The reduction gearbox was broken away from the crankcase exposing the gear assembly. All six cylinders and associated overhead components were intact. Drive train continuity, valve actuation and cylinder compression was established by rotating the crankshaft. The oil sump was broken open. The interior of the engine was visually inspected through the opening in the oil sump. The crankshaft, connecting rods and counterweights were intact. Both magnetos and their respective ignition harnesses sustained extensive thermal damaged and were partially melted away. The vacuum pump was partially broken away from its respective mounting pad. The vacuum pump drive coupling was fractured, however, the internal components of the pump were intact and unremarkable. The spark plugs sustained extensive thermal damage, however, exhibited normal operating wear patterns. The DC generator was partially broken away from its respective mounting pad. The engine's carburetor, which was partially broken away from the engine, was dissembled. Both metallic type floats had melted away from the float arm assembly and were resting in the float chamber. The float chamber was free of contaminants, with the exception of the solder from the float arm. Post-accident inspection and teardown of the airplane's engine revealed no evidence of a mechanical malfunction or failure. On August 29, 2000, the airplane wreckage and associated components were released to the owner's estate in Portland, Oregon. The commercial pilot was participating in a group fly-in from Aurora, Oregon, to Lebanon, Oregon. After failing to arrive at the intended destination and not returning to his home, family members contacted the FAA and a search for the pilot and aircraft was initiated. The following day the aircraft wreckage was located in a wooded area southeast of Molalla, Oregon. The aircraft collided with mountainous terrain and was destroyed. Post-accident examination of the airplane and engine revealed no evidence of a preexisting mechanical malfunction or failure. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_SEA00FA127.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 (maintenance). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NTSB Aircraft Accident Reports 2019 · Accident report
Embraer ERJ 175 Runway Excursion at Charlotte Douglas
Republic Airline ERJ-175 runway excursion CLT, January 2018. Examines a low-energy runway excursion involving misuse of autobrakes + thrust reverser response after a high-crosswind landing on a contam…
- Embry-Riddle Scholarly Commons 2026 · Journal article (IJAAA)
From Reactive to Predictive: A hybrid Trust-Mediated Adoption Framework for Data-Driven Maintenance in Distributed-Authority Aviation Environments
Modern aviation maintenance operates within increasingly data-intensive technological environments, yet the operational integration of predictive maintenance into routine decision-making remains incon…
- Semantic Scholar 2025 · Article (Applied Sciences)
Decision-Making Framework for Aviation Safety in Predictive Maintenance Strategies
The implementation of predictive maintenance (PM) in aviation presents unique challenges due to strict safety requirements, complex operational environments, and regulatory constraints.
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
Low-Resource Automatic Speech Recognition Domain Adaptation – A Case-Study in Aviation Maintenance
With timeliness and efficiency being critical in the aviation maintenance industry, the need has been growing for smart technological solutions that optimize and streamline the different underlying ta…
- Embry-Riddle Scholarly Commons 2024 · Journal article (JAAER)
A New Trajectory in UAV Safety: Leveraging Reinforcement Learning for Distance Maintenance Under Wind Variations
In the field of aviation, safety is a critical cornerstone, and the operation of Unmanned Aerial Vehicle (UAV) systems is deeply connected with this principle.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Just Culture in Aviation: A Metaphorical Study on Aircraft Maintenance Students
Just Culture, a sub-dimension of safety culture, has been a prominent and debated topic in aviation safety in recent years.
Browse the full corpus — academia portal ↗