NTSB CAROL · Event
Event SEA00FA014
Aircraft involved
Probable cause & findings
Failure to maintain clearance from the runway surface while maneuvering at low altitude, and inadequate remedial action after the tail rotor struck the surface.
Factual narrative
HISTORY OF FLIGHT
On November 2, 1999, at 1532 Pacific standard time, an Enstrom F28C helicopter, N635H, was destroyed when it sustained a tail rotor blade strike during a solo instructional flight at Pendleton airport, Pendleton, Oregon. The airline transport pilot, who was preparing for a commercial rotorcraft-helicopter rating, was fatally injured. The helicopter was registered to Charlie Inc., an entity of which the pilot was a principal. Visual meteorological conditions prevailed at the time of the flight. No flight plan was filed. There was a post-impact fire. No ELT was installed in the aircraft. According to the pilot's flight instructor, he had accumulated approximately 66.5 hours of helicopter instruction, and was scheduled for an add-on commercial rating on the day following the accident. The instructor had flown once with the pilot for 1.7 hours the morning of the flight. The pilot had then flown again for approximately an hour in an additional flight before the accident flight. On the accident flight, the pilot was on his second left-hand circuit of the pattern for runway 34. According to the tower controller, the pilot had been cleared for the option on runway 34 on his first circuit . He had made three touchdowns along the length of runway 34, at the threshold, mid-length, and at the departure end of the runway, then had continued his circuit. On the second circuit, the tower controller had again cleared the pilot for the option. The tower controller observed similar touchdowns at the threshold, and at mid-field. He stated that he was looking away at the time of the crash; however he heard a very garbled transmission, looked in the direction of the helicopter, saw dirt flying, and activated the siren and dispatched rescue vehicles. He then saw smoke and flames. Ground strikes consistent with tail rotor blade strikes were found near the wreckage. Both tail rotor blades separated from the tail rotor hub, and the tail rotor gearbox also separated from the tailcone. The pilot was at least partially ejected from the helicopter's cockpit and was partially beneath the fuselage when rescuers arrived. Rescuers lifted the fuselage and pulled him from the burning wreckage.
WRECKAGE AND IMPACT INFORMATION
The wreckage was located along the east edge of runway 34, a few hundred feet from the departure end of the runway. Two groups or sets of surface scars were found on the asphalt runway surface. The first set included a gouge estimated to be about 1/4 inch deep and one inch in diameter, with a 4-5 inch scratch or metal and paint transfer. A few inches away were three other scrapes or gouges. This set of marks was to the right of the runway centerline. The second surface scar location was about 20 yards closer to the departure end of the runway, and on the left side of the runway centerline, consisting of another similar crater, with an associated 4-5 inch scratch mark. In both instances, flecks of paint and material similar to that used for tail-rotor bonding were found in the vicinity. One tail rotor blade, including the grip, was found a few yards from the first surface scars, closer to the approach end of the runway. The tail rotor gearbox was found about twenty yards north of the second surface scar, also on the left side of the runway centerline. The second tail rotor blade was found beyond the gearbox, again to the left of the runway centerline. The tail rotor blade nearest the approach end of the runway exhibited large radius bending, and two separate areas of compression folds on the trailing edge. The other tail rotor blade exhibited trailing edge folding, large radius bending from about mid-span, and leading edge crushing and impact signatures. The tail rotor gearbox exhibited a broken casting, and the two associated control cables exhibited signatures similar to tensile overload. One blade grip remained attached to the spindle; the other blade grip remained with the other rotor blade. The fuselage was found laying on its left side, with the tailboom separated from the fuselage aft of the engine. The upper fuselage and cockpit area exhibited fire damage, as did both the upper and lower area aft of the passenger compartment bulkhead. The belly exhibited arcing scratches in the paint and crushing. The left skid was folded beneath the fuselage. The right skid was bent forward of the front attachment point; the forward portion of that skid exhibited abrasion and scratches at an angle to the skid tube's longitudinal axis. The tail rotor hoop had separated into two main pieces, which were located separately in the wreckage distribution. No evidence of scratches, scoring, or paint transfer was observed on the outer surface of the hoop. Control continuity was established from the cyclic and collective controls to the swash plate. Pedal cables were, as earlier described separated. All three main rotor blades exhibited tip damage and delamination consistent with blade strikes. No pre-impact mechanical anomalies were noted during the on-scene investigation. The helicopter was equipped with seat belts. No evidence of installed shoulder harnesses was found. The pilot's seat belt buckle remained buckled when observed at the accident scene. The belt was found outside the aircraft. Its right-side attachment point remained clasped on its attachment point; however the attachment point had separated from the airframe. The other end of the belt exhibited melting and separation.
MEDICAL AND PATHOLOGICAL INFORMATION
An autopsy of the pilot was performed November 3, 1999 by Dr. James B. Sawyer of Blue Mountain Pathology, Inc., in Pendleton, Oregon. Toxicological testing was conducted by the FAA laboratory, with negative results for carbon monoxide, cyanide, and ethanol.
FIRE
The tower controller activated the siren and dispatched fire/rescue personnel after observing the crash. Vehicles were en route to the accident scene within 4 minutes of notification. The fire was suppressed using foam.
ADDITIONAL INFORMATION
The wreckage was released to the insurance adjuster, as owner's representative, on November 4, 1999, after inspection by investigators. At the time of release the wreckage was located at the General Aircraft Services, Inc., facility in Pendleton, Oregon. The helicopter was destroyed when it sustained a tail rotor blade strike during a solo instructional flight. The airline transport pilot, who was preparing for a commercial rotorcraft-helicopter rating checkride on the following day, was fatally injured. The pilot was on his second left-hand circuit of the pattern and had been cleared for the option. On his first circuit, he had made three touchdowns along the length of the runway, at the threshold, mid-length, and at the departure end, then had continued his circuit. On the second circuit, the tower controller had again cleared the pilot for the option. The tower controller observed similar touchdowns at the threshold, and at mid-field. He stated that he was looking away at the time of the crash; however he heard a very garbled transmission, looked in the direction of the helicopter, saw dirt flying, and activated the siren and dispatched rescue vehicles. Ground strikes consistent with tail rotor blade strikes were found near the wreckage. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_1999_SEA00FA014.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 (stall). 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 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- arXiv 2023 · arXiv preprint
Automating Bird Diverter Installation through Multi-Aerial Robots and Signal Temporal Logic Specifications
This paper tackles the task assignment and trajectory generation problem for bird diverter installation using a fleet of multi-rotors.
- arXiv 2023 · arXiv preprint
Variation of Critical Crystallization Pressure for the Formation of Square Ice in Graphene Nanocapillaries
Two-dimensional square ice in graphene nanocapillaries at room temperature is a fascinating phenomenon and has been confirmed experimentally.
- arXiv 2023 · arXiv preprint
Polycrystallinity enhances stress build-up around ice
Damage caused by freezing wet, porous materials is a widespread problem, but is hard to predict or control. Here, we show that polycrystallinity makes a great difference to the stress build-up process…
- arXiv 2022 · arXiv preprint
Enhanced Prediction of Three-dimensional Finite Iced Wing Separated Flow Near Stall
Icing on three-dimensional wings causes severe flow separation near stall. Standard improved delayed detached eddy simulation (IDDES) is unable to correctly predict the separating reattaching flow due…
- Embry-Riddle Scholarly Commons 2021 · Journal article (JAAER)
Analysis on the Negative Emotional, Physiological, and Cognitive Responses Elicited from of the Activation of a Stall Alarm
Failing to identify an aerodynamic stall can lead to the inability of an aircraft to sustain flight. To warn pilots of an impending or fully-developed stall, many aircraft have safety devices installe…
Browse the full corpus — academia portal ↗