NTSB CAROL · Event
Event LAX02LA014
Registry · N3246G
FAA Aircraft Registry record.
Make / Model
NORTH AMERICAN SNJ-5
Year of manufacture
1959 · 42 years old at event
Engine
P&W R1340 SERIES (600 hp)
Seats / Engines
2 seats · 1 engine
Last airworthiness date
19620426
ADS-B equipped
Yes — Mode-S A3805D
Registrant of record
AMERICAN AIRPOWER HERITAGE FLYING MUSEUM INC
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
The pilot's inadequate compensation for an existing crosswind condition, and failure to maintain directional control on the landing rollout.
Factual narrative
On October 23, 2001, at 1449 mountain standard time, a North American SNJ-5, N3246G, struck a runway distance marker sign on the landing rollout from runway 22L at the Falcon Field Airport (FFZ), Mesa, Arizona. The airplane was owned by the Confederate Air Force and rented by the pilot under the provisions of 14 CFR Part 91. The airplane sustained substantial damage when the wing struck the marker sign. The airline transport pilot, the sole occupant, was not injured. Visual meteorological conditions prevailed for the local area personal flight that departed Falcon Field about 1400. According to the owner/operator of the airplane, the pilot landed on the runway centerline with a right crosswind. On the landing the airplane started to depart to the right of the runway. The pilot attempted to keep the airplane from ground looping; however, it departed the runway and struck a sign. The pilot stated that after the airplane came back onto the runway he knew that he had hit something, and thought it was the runway distance marker sign. He taxied back to the operator's hangar. In the pilot's written statement to the Safety Board he reported that during the preflight he added 1 1/2 quarts to the existing 8 gallons, and had the fuel tanks topped off, bringing the total fuel to 110 gallons. He filed an interorganizational flight plan for a local area flight 1 hour in duration. He stated that this was a proficiency flight. He taxied to the run-up area, conducted the before takeoff checklist, and was cleared to takeoff with a departure from the downwind eastbound. He conducted maneuvers and then returned to Falcon Field. The pilot stated about 10 miles out for landing he contacted the local controller and requested a clearance to land with information x-ray. The local controller cleared him for a straight-in approach for runway 22L with instructions to report on 3-mile final. He contacted the local controller on a 3-mile final and was cleared to land. The local controller informed him that that the reported winds were from 290 degrees at 8 knots. The pilot reported that he conducted the before landing checklist and kept his approach speed at 85 knots. He indicated that in a normal approach he would have been at 80 knots, but because of the existing crosswind he opted to carry "a little extra speed should difficulty be encountered." The pilot stated that he had planned for a full stall landing, and that the final portion of his approach was normal. He added right aileron to counteract the crosswind and maintain directional control, as well as runway alignment. After touchdown, he applied full right aileron and the control stick was held in its full aft position. On the landing rollout he had to increase the left rudder input. He stated that he "sensed a side load on the airplane," and that it started to move to the right of the runway. He applied full left rudder; however, the turn to the right increased. He maneuvered to avoid a black box on the right edge of the runway by inputting left brake. He felt that a ground loop was imminent if he continued applying brake pressure, so he released the pressure and departed the runway in "a stable condition." The pilot stated that he applied power and taxied back onto the runway. The local controller inquired if he needed assistance, and he replied in the negative. He asked if he could taxi back along runway 22L and make sure that he had not struck any runway signs. The local controller informed him during his taxi that he had struck a runway distance marker. He then asked for a 180-degree turn to the ramp to return to the Confederate Air Force ramp. According to the pilot, he spoke with the tower chief at FFZ. At 1459, a special weather observation report was issued; winds were reported from 290 degrees at 15 knots. The pilot further stated that the crosswind limit for the airplane was 15 knots. A Federal Aviation Administration inspector examined the airplane. He found nothing mechanically wrong with the brake or rudder system. On the landing rollout the airplane veered off to the right of the runway and impacted a runway distance marker. This was a proficiency flight. The pilot noted no control problems with the airplane while he was conducting maneuvers. After he was cleared to land, the local controller issued winds from 290 degrees at 8 knots. The pilot decided to make the approach at a higher airspeed in case he encountered any problems with the landing due to the exisitng crosswind. Prior to touchdown the pilot made a crosswind correction with right aileron to aid in maintaining directional control and runway alignment. After touchdown he applied full right aileron and noted that the control stick was in the full aft position. On the landing rollout he increased left rudder input because the airplane had started to move towards the right of the runway. He applied full left rudder; however, the turn continued to increase. He utilized the left brake to maneuver around an obstruction on the runway. He felt that a ground loop was imminent, released the brakes, and departed the runway. The airplane rudder and brake systems were inspected with no discrepancies noted. Wind direction and velocity issued as a result of the accident were from 290 degrees at 15 knots. The crosswind limitation for the accident airplane was 15 knots. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2001_LAX02LA014.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 ↗