NTSB CAROL · Event
Event SEA00LA172
Aircraft involved
Probable cause & findings
Aircraft control was not maintained during approach for landing.
Factual narrative
HISTORY OF FLIGHT
On August 26, 2000, about 1500 mountain daylight time, a Cessna 411, N411TK, registered to Aircraft Emporium Inc, and operated by the private pilot as a 14 CFR Part 91 personal flight, veered off the approach to runway 28L and collided with the terrain about one mile short of the runway at Boise, Idaho. Visual meteorological conditions prevailed and no flight plan was filed. The aircraft was substantially damaged and the pilot and his passenger were seriously injured. The flight originated from Las Vegas, Nevada, about 1200 Pacific daylight time. Due to injuries to both the pilot and passenger, neither occupant recalls the events leading up to the accident. The Federal Aviation Administration reported that the aircraft was on approach to runway 28L when it suddenly veered to the left of course. The aircraft subsequently collided with the terrain about one mile short of the runway, and about one-quarter of a mile to the south of the approach path. Witnesses in the area reported that the aircraft was observed on the approach when it banked to the left and descended to the ground. Another witness reported that the aircraft was "...rocking back and forth (right and left) approx. 500' over his head..." on the north side of Gowen Rd, prior to it descending to the ground. The pilot reported that he was in the process of purchasing this aircraft from an aircraft broker in Corona, California, and that the aircraft was being "test flown for possible purchase." The flight began in Corona, California, on the morning of August 26, with a fuel stop in Las Vegas, Nevada. The flight then continued on to its final destination to Boise, Idaho.
PERSONNEL INFORMATION
The pilot holds a private pilot certificate and rated for single and multi-engine land (MEL) aircraft. Flight logbook four was provided for review. The first logbook entry was dated June 5, 1999. The last entry was dated August 8, 2000. At the time of the accident, the logbook indicated that the pilot had accumulated a total flight time in all aircraft of approximately 2,539 hours. Approximately 36 hours total time (dual received and pilot-in-command) had been accumulated in MEL aircraft, with approximately 26 hours logged as pilot-in-command (PIC). Approximately 20 of those hours were logged as PIC prior to the MEL check ride dated August 2, 2000. After the check ride, to include the approximate 3 hours flight on the day of the accident, the pilot logged approximately six hours as PIC. On June 22, 2000, the logbook indicated a 36-minute introduction dual flight in the Cessna 411. Although the entry indicated the registration number for the accident aircraft, the pilot reported that it was entered in error and was in another Cessna 411 that the broker had available. The pilot reported that there was one other flight in the Cessna 411, but that it did not get entered in the logbook. The logbook also indicated from July 7 to July 9, 2000, 10.3 hours logged as "second-in-command" for ferry flights in a Cessna 337.
AIRCRAFT INFORMATION
Maintenance records obtained for review indicated that the aircraft had been signed-off for an annual inspection on August 8, 2000. The entries for the airframe and engines indicated that a discrepancy list was provided to the owner/operator. The aircraft had not been returned to an airworthy condition. The discrepancy list (see attachment) indicated that several items, to include evidence of leaking auxiliary fuel tanks, had not been accomplished. When asked, the pilot reported that he was not aware that the aircraft was not airworthy, and was told by the aircraft broker that it was okay to take the aircraft for the flight to Boise. In the pilot's attached statement, he indicated that the broker had informed him that, "...the auxiliary tanks leaked when completely filled to the top." Fuel records indicate that the aircraft was fueled at the Corona Municipal Airport on the morning of August 26, 2000. A total of 18.9 gallons of 100LL fuel was purchased. Another fuel receipt from Eagle Aviation Resources, Las Vegas, indicated 34.5 gallons of fuel was purchased that same day. The pilot reported that he does not recall the fuel quantity prior to the departures or to which fuel tanks the fuel was added. The auxiliary fuel tanks (wing tank) hold 35 useable gallons in each wing. The main tanks (wingtip) hold 50 useable gallons in each tip tank.
WRECKAGE AND IMPACT INFORMATION
The Boise Airport Police prepared a wreckage diagram of the accident site. The diagram identified ground signatures noted on the north side of Gowen Road indicating that the aircraft contacted the ground in a wings level, nose down attitude. The aircraft slid approximately 150 feet before coming to rest on its belly partially obstructing the road. The left side propeller assembly separated from the crankshaft and was on the opposite side of the road. The propeller blades remained attached in the hub. The left side main fuel tank (tip tank) separated from the left wing and was found in close proximity to the fuselage. The tank was compromised and a small amount of fuel remained in the cell. The right side main fuel tank remained attached to the wing, however, the cell was compromised and a small amount of fuel remained in the cell. The auxiliary fuel tanks (wing tanks) were found empty during the follow-up wreckage inspection. Fire department personnel reported a fuel spill at the accident site; however, the investigative team could not verify an amount. Fire suppression foam had been applied to the accident site upon Fire Department arrival.
ADDITIONAL INFORMATION
Western Aircraft, Boise, ID, removed the wreckage from the accident site and transported it to their facility at the airport. At this facility both engines were inspected. During the inspection it was noted that the spark plugs on both engines exhibited heavy electrode erosion and wide gapping. It also appeared that the exterior of the spark plugs had been bead blasted and then painted with bright silver/chrome paint. The turbochargers were free to turn and their bearing had nominal clearance. Both metering unit fuel inlet screens were removed and found to be clear of contaminants. Minimal fuel was present in the screen cavities. The throttle control positions in the cockpit were found in the aft position, however, the throttle controls at the engines were found 7/8 open. The cockpit mixture controls were found to be mid-range for the left engine and full forward for the right. The mixture controls at the engines were found in the full rich position. Further inspection of both engines did not reveal evidence of a pre-impact malfunction or failure. Documentation of the cabin noted that both fuel selectors were positioned to the auxiliary fuel tanks. The Cessna 411 Owner's Manual indicates that for landing, the fuel selectors are to be selected to the main tanks (see attachment). Control continuity was established from the ailerons, flaps, rudder and elevator to the cockpit area. The aileron, rudder and elevator trim tab positions were neutral. The landing gear selector was down. The flaps were extended. The Federal Aviation Administration reported that this aircraft had been based in Van Nuys, California, and unused for several years. The Van Nuys Flight Standards District Office had revoked the airworthiness certificate until maintenance items (see attachment) were accomplished prior to the approval for a special ferry permit for a flight to the Corona airport. The wreckage was released to the owner on August 31, 2000. While within a two mile final to the runway, the airplane suddenly veered to the left of the approach and descended to the ground. The aircraft collided with the level terrain in a wings level and nose down attitude. The aircraft slid about 150 feet before coming to rest on its belly next to a road. The fuel cells were compromised and there was evidence of a fuel spill of unknown quantity. During the follow-up wreckage inspection, there was no evidence found to indicate a mechanical failure or malfunction. Inspection of the maintenance logbooks found that although the aircraft had been signed-off for an annual inspection, there was several discrepancy items noted, to include leaking fuel cells, which had not yet been repaired/replaced, and the aircraft was not signed off in an airworthy condition. This discrepancy list was given to the owner/operator. The pilot, who was in the process of purchasing this aircraft from an aircraft broker, stated that he was unaware that the aircraft was not airworthy, and was told by the broker that it was okay to fly the aircraft. The pilot was however, aware of the leaking fuel cells. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2000_SEA00LA172.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 2020 · Conference paper
Under Pressure: Decision Making in Aircraft Maintenance and the Role of Gender
In aircraft maintenance, leaders are under near-constant pressure to maintain airworthiness. Every minute an aircraft cannot fly due to maintenance represents financial waste.
- 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 ↗