NTSB CAROL · Event
Event SEA05FA061
Aircraft involved
Probable cause & findings
The total loss of engine power immediately after takeoff for undetermined reason.
Factual narrative
HISTORY OF FLIGHT
On March 12, 2005, at 1038 Pacific standard time, a Navion, Navion H, N2512T, was substantially damaged during a forced landing attempt, following a loss of engine power near Lenhardt Airpark, Hubbard, Oregon. The commercial pilot was critically injured and his passenger was seriously injured. The pilot/owner was conducting the flight under Title 14 CFR Part 91. Visual meteorological conditions prevailed for the cross-country personal flight which was originating at the time of the accident. A flight plan had not been filed. In a telephone interview with the pilot, he said that he used a check-list to preflight the airplane, and that he checked the fuel tanks for contamination. He said that he started the engine with the fuel selector in the both position, and taxied with it in the left main position. He performed his engine run-up with the fuel selector in the right main position; he said the engine performed normally. The pilot said that as he took the active runway 02 for takeoff, he switched the fuel selector to the both position. On June 21, 2005, the pilot submitted a written statement which said: "As I taxied to the departure end of Rwy 02 I cycled the fuel selector valve from L to R and back to Main with no interruption of engine operation." He further said that the airplane's engine run up was normal and the takeoff was normal until immediately after takeoff when the engine quit with no sputtering or surging. Witnesses said that the airplane had just taken off, when the engine appeared to lose power. The pilot performed a forced landing into a Christmas tree farm. The engine mount was bent, the right wing, fuselage, and empennage were bent, wrinkled, and twisted.
PERSONAL INFORMATION
The pilot's most recent Federal Aviation Administration (FAA) flight medical exam (second class) was on January 14, 2004, and at that time he reported on his application that he had 425 hours of flight experience. It was estimated that he had 460 hours of flight experience at the time of the accident. The pilot was nearing the completion of his Flight Instructors training.
AIRCRAFT INFORMATION
The airplane was a non-pressurized, single engine, propeller-driven, five seat airplane, which was manufactured by Navion Aircraft Corporation, in 1968. The airplane had a maximum takeoff gross weight of 3,315 pounds. It was powered by a Continental IO-520-B, reciprocating, normally-aspirated, fuel injected, direct-drive, air-cooled, horizontally-opposed, six-cylinder engine, which had a maximum takeoff rating of 285 horsepower at sea level. Maintenance records indicate that the last annual inspection was completed on June 2, 2004, and at the time of the accident, the airplane had 5,093 hours of flight. The pilot had equipped the airplane with an engine data management system, EDM-700, from J.P. Instruments. He subsequently had GAMI (General Aviation Modifications, Incorporated) fuel injection nozzles put in the engine.
METEOROLOGICAL INFORMATION
At 1053, the weather conditions at Aurora State Airport, Aurora, Oregon (elevation 196 feet), 320 degrees for 4 nautical miles (nm) from the accident site, were as follows: wind 030 degrees at 11 knots, gusting to 16 knots; visibility 10 statue miles; cloud condition clear; temperature 60 degrees Fahrenheit; dew point 45 degrees Fahrenheit; altimeter setting 30.23 inches.
AIRPORT INFORMATION
The Lenhardt Airpark (elevation 165 feet), Hubbard, Oregon, is not serviced by a control tower. The airpark has one runway: 02-20 which is 3,200 feet long and 40 feet wide. Both ends of the runways are VASI (Visual Angle Slope Indicator) equipped. The airpark is serviced by a CTAF (Common Traffic Advisor Frequency) of 122.9 MHz.
WRECKAGE AND IMPACT INFORMATION
The airplane was found approximately 500 feet, 90 degrees to the right of the departure end of runway 02 (N45 degrees, 10', 58"; W122 degree, 44', 21"; elevation 145 feet). The airplane impacted 6 to 8 foot high Christmas trees and created an approximate 50 foot path through them on an orientation of approximately 110 degrees. The longitudinal orientation of the airplane was approximately 140 degrees. All of the airplane's major components were accounted for at the accident site. On April 19, 2005, the engine was test run through its full power band at the Troutdale Airport, Portland, Oregon. No preimpact engine or airframe anomalies, which might have affected the airplane's performance, were identified.
MEDICAL AND PATHOLOGICAL INFORMATION
No toxicology tests were performed on the pilot; he was hospitalized with critical injuries (predominately to the head).
SURVIVAL ASPECTS
The airplane was not equipped with shoulder harnesses. The pilot stated that he believes that his head injuries would have been significantly less, if he had been wearing shoulder harnesses.
TESTS AND RESEARCH
The airplane's EDM-700 was sent to the manufacturer for read-out of its storage data card. The data indicated that all six of the engine cylinder's EGTs (exhaust gas temperatures) dropped simultaneously. No engine anomalies were identified by the read-out.
ADDITIONAL INFORMATION
The airplane, including all components and logbooks, were released to a representative of the owner's insurance company, on April 20, 2005. The pilot said, in a telephone interview, that he used a check-list to preflight the airplane, and he checked the fuel tanks for contamination. He said he started the engine with the fuel selector in the both position, and taxied with it in the left main position. He performed his engine run-up with the fuel selector in the right main position. The pilot said that as he took the active runway 02 for takeoff, he switched the fuel selector to the both position. Witnesses said that the airplane had just taken off, when the engine appeared to lose power. The pilot performed a forced landing into a Christmas tree farm. He was critically injured during the landing; he was not wearing shoulder harnesses. On June 21, 2005, the pilot submitted a written statement which said: "As I taxied to the departure end of Rwy 02 I cycled the fuel selector valve from L to R and back to Main with no interruption of engine operation." He further said that the airplane's engine run up was normal and the takeoff was normal until immediately after takeoff when the engine quit with no sputtering or surging. The engine mount was bent, the right wing, fuselage, and empennage were bent, wrinkled, and twisted. The engine was test run through its full power band. No preimpact engine or airframe anomalies, which might have affected the airplane's performance, were identified Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2005_SEA05FA061.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.
- 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.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Performance PRISM: A Comprehensive Framework For Performance Measurement In Aircraft Maintenance
Aircraft maintenance is governed by rigorous safety requirements and high operational complexity, demanding robust performance measurement frameworks to ensure optimal maintenance practices.
Browse the full corpus — academia portal ↗