NTSB CAROL · Event
Event SEA99LA009
Aircraft involved
Probable cause & findings
The pilot-in-command's failure to maintain directional control. Contributing factors were the uneven taxiway, inadequate airport maintenance (temporary threshold marking) by the airport management, and a ditch alongside the taxiway.
Factual narrative
On October 23, 1998, approximately 1700 mountain daylight time, a Pitts S-1, N144JS, registered to and being flown by a private pilot, was substantially damaged during a loss of control on landing at the McCall airport, McCall, Idaho. The pilot was uninjured. Visual meteorological conditions prevailed and no flight plan had been filed. The flight, which was personal, was to have been operated under 14CFR91, and originated from McCall approximately 1610. The pilot, interviewed by an inspector from the Federal Aviation Administration's Boise Flight Standards District office, reported that he taxied out and departed on runway 34 after determining it was clear, flew a short while and then returned to land. He further reported to the inspector that "on downwind to 34 he saw the large white X on the runway. He did a fly-by to evaluate the runway/taxiway and vacillated on weather [sic] to land on the runway or taxiway. There was no wind and weather was not a factor. He elected to land on the taxiway headed toward the north. As he approached and began the flair [sic] he lost sight over the nose of the aircraft and transitioned to looking out the left side (this is normal operation of a Pitts). All he could see was the grass of the infield, not having the edge of the taxiway to follow he feels this is why he lost directional control. He stated he bounced on landing, further complicating the situation. The right wheel went off the taxiway and the aircraft veered right and went into the drainage ditch ending up on its nose." (Refer to ATTACHMENT FAA-I). The pilot provided a schematic showing where he touched down on the taxiway. This schematic showed the touchdown point approximately 500 feet north of the south end of the parallel taxiway (refer to DIAGRAM I). The pilot also reported on NTSB Form 6120.1/2 that the aircraft suffered no mechanical malfunction or failure at the time of the accident. According to the current US Government Flight Information Publication, the McCall airport is equipped with a single north/south asphalt runway (16/34) which measures 6,126 feet in length and 75 feet in width. A single, parallel asphalt taxiway of about the same length and 50 feet in width exists slightly east of the runway. The airport manager reported that he had "NOTAM-ed the runway closed Oct. 20th (refer to ATTACHMENT N-I) and advised pilots to operate on the parallel taxiway (which had been marked as a runway in its own right prior to this summer) as long as they did not require more than 4,962 feet of runway. There is a hump in the pavement at an exit taxiway intersection 1,200 feet from the south end (refer to DIAGRAM I), so I had placed temporary displaced threshold markings in the grass next to the parallel taxiway and advised pilots to land north of that point" (refer to ATTACHMENT AM-I and ATTACHMENT AM-II). In a telephone conversation with the Fixed Based Operator (FBO), he reported that frequent miscommunications existed during the construction phase between the FBO (UNICOM operator) and airport management. This resulted in the FBO occasionally providing contradictory information as to the availability of runway 16/34 versus the parallel taxiway for operations. Additionally, he reported that the displacement at the south end of the parallel taxiway was poorly marked. This marking consisted of plywood which had not been painted in a conspicuous color and was placed in the grass alongside the taxiway at the intended displacement location. Upon return to the airport after a local flight, the pilot-in-command ascertained that the single north/south runway was closed. He then initiated an approach to the 50-foot wide asphalt parallel taxiway which had been NOTAM'ed by airport management as the alternate landing runway during runway closure. The pilot touched down short of the 1,200 foot displaced threshold of the landing taxiway and rolled over a hump during which the aircraft bounced. The pilot then lost directional control and the aircraft rolled off the taxiway into a drainage ditch alongside the taxiway, coming to rest in a nose-over attitude. The displacement to the taxiway threshold (upwind of the hump) was reported by the FBO to consist of plywood which had not been painted in a conspicuous color and was placed in the grass alongside the taxiway at the intended displacement location. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1998_SEA99LA009.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 (loss of control, 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.
- NASA NTRS 2019 · Poster
Combining GOES-16 and Surface Ceilometer Data to Improve Cloud Ceiling Estimates over the U.S.
To better address the low ceiling hazard to aviation, a hybrid approach is taken that utilizes satellite data to extend cloud ceiling information contained in surface station observations to much wide…
- NASA NTRS 2011 · Conference Paper
TSS-1R Failure Mode Evaluation
Soon after the break of the tether during the Tethered Satellite System (TSS-1R) mission in February, 1996, a Tiger Team was assembled at the George C.
- NTSB Aircraft Accident Reports 2002 · Accident report
Loss of Control and Impact with Pacific Ocean — Alaska 261
Alaska Airlines Flight 261 (MD-83) Pacific Ocean, January 31, 2000 — 88 fatalities. Definitive investigation of the Alaska 261 pitch-runaway-and-loss-of-control crash.
- 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…
- Embry-Riddle Scholarly Commons 2025 · Journal article (JAAER)
A Scoping Review of Aviation Loss of Control Inflight Research
Loss of control – inflight (LOC-I) contributes to aircraft accidents at unacceptably high rates. Significant industry efforts and research have aimed to improve LOC-I prevention, detection, and recove…
- 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.
Browse the full corpus — academia portal ↗