NTSB CAROL · Event
Event LAX04LA297
Registry · N40AW
FAA Aircraft Registry record.
Make / Model
AVIAT AIRCRAFT INC A-1A
Year of manufacture
1999 · 5 years old at event
Engine
LYCOMING O&VO-360 SER (180 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
19990304
ADS-B equipped
Yes — Mode-S A4AA5D
Registrant of record
KLINGBEIL MARK T
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's failure to maintain an adequate airspeed on final approach, which resulted in an inadvertent stall and a hard landing.
Factual narrative
On April 19, 2004, at 1800 Pacific daylight time, an Aviat A-1A (Husky) airplane, N40AW, veered off the landing area and collided with a parked airplane during landing at Visalia Municipal Airport, Visalia, California. The airline transport pilot and one passenger were not injured; both airplanes sustained substantial damage. The pilot was operating the borrowed airplane under the provisions of 14 CFR Part 91. Visual meteorological conditions prevailed, and no flight plan had been filed. The airplane departed from the Visalia airport at 1700 for the local area pleasure flight. According the to Federal Aviation Administration (FAA) inspector, the pilot was landing on an unimproved and undesignated area of the airport. While the Husky was on final approach, another airplane taxied across its flight path. When the Husky touched down, it veered from the pilot's intended landing surface and collided with a parked airplane, N8321X, a Piper PA-28RT-201T (Turbo Arrow IV). The Husky sustained substantial damage to the right wing that included crush on the leading edge at the center point of the wing. Additionally, a compression strut located approximately midspan and between the fore and aft wing spars was bent upward and outward at its lower surface. The Arrow's horizontal stabilator, which is attached to the upper portion of the vertical stabilizer, was torn from the empennage. An FAA inspector was informed of this accident on August 18, 2004, via an anonymous phone call. Witnesses contacted at the airport verified the story as relayed in the phone call. The FAA inspector notified the National Transportation Safety Board investigator-in-charge (IIC) of this accident on August 19, 2004. In a written statement submitted to the IIC, the pilot reported landing on the grass, adjacent to the taxiway. As he turned the airplane toward his hangar, it struck a parked airplane. The parked airplane was near the grass landing area. The pilot further reported that he could not see the parked airplane over the nose of his tailwheel equipped airplane. The pilot did not report any mechanical malfunctions with the airplane prior to the accident. The FAA inspector, who had been notified of the accident, interviewed the pilot on August 23, 2004. The pilot reported that he set up for a landing on an unpaved surface between the parallel taxiway for runway 30 and the paved parking ramp. During the landing approach, the pilot observed a multiengine airplane taxiing toward the ramp area. This multiengine airplane became a potential conflict for the pilot. The pilot slowed the airplane and then landed, stopping in about 200 feet. The pilot taxied the airplane and rushed to arrive at the hangar area. As he began taxiing the airplane, the right wing collided with the tail of a parked airplane. After separating the airplanes, the pilot continued taxiing his airplane. The pilot acknowledged to the inspector that the airport manager had verbally instructed him not to use the grass area for takeoffs and landings. He did not report the accident because he believed it was not a reportable accident. A witness to the accident, a student pilot, submitted a statement. The witness was attending ground school at a flight school located at the airport. His ground instructor was instructing the class on preflight procedures of a Cessna 172 in the tie-down area. During the instruction, the witness observed a high-wing tailwheel equipped airplane landing parallel to runway 30, about halfway down and to the east of the runway and taxiway. The altitude of the airplane was approximately 100 to 150 feet above ground level (agl). After the airplane passed the witness, his attention returned to the ground school lesson. About 3 to 4 seconds later, the witness heard a loud noise and looked up to see the tailwheel-equipped airplane spinning around to the airplane's left in a cloud of dust. A Piper T-tail parked on the ramp was missing its tail section. The top of the tail was resting on the leading edge of the wing of the tailwheel-equipped airplane. The occupants of the tailwheel-equipped airplane carried the tail back to the Piper, located about 100 feet from where the tailwheel-equipped airplane came to rest. An additional witness, a private pilot, observed the Husky on downwind for runway 30. He was later surprised to see it on short final, almost overhead at an altitude of 100 feet. The airplane appeared to be lined up for touchdown on a grass area between the taxiway and the paved parking area. As the Husky passed approximately 50 feet over the taxiway, another airplane turned onto the taxiway, in close proximity to the Husky. The Husky appeared to flare and the right wing dropped "as though it may have stalled." The wing appeared to hit the ground; the airplane bounced and eventually returned to a three-point attitude, but began to ground loop. As the airplane spun, it collided with the tail section of an airplane tied down adjacent to the grass area. The tail section of the parked airplane was completely sheared off and tangled under the Husky. The Husky occupants removed the tail section and then taxied from the accident scene. The airplane landed hard, ground looped, and collided with a parked airplane. The pilot was landing on an unimproved, unauthorized area of the airport. During final approach, an airplane taxied in front of him and presented a potential conflict. According to a witness, the pilot flared the airplane and the right wing dropped, "as though it may have stalled." The right wing impacted the ground and then the airplane returned to a three-point attitude. The airplane then ground looped and impacted an airplane parked on the ramp. Prior to the accident, the airport manager verbally informed the pilot that he was only to use the designated runways as landing areas. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2004_LAX04LA297.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 ↗