Premium research interface

The modern interface for aviation safety intelligence.

Search investigations, review source evidence, monitor watched reports, and trace long-term patterns from one calm, data-first workspace.

63k+
Reports indexed
1940-2026
Coverage
Recent
Last data refresh
Featured Report

Loading…

Loading featured report…

Loading…
Open Report

Safety trends by operating rule

Track fatal and non-fatal accident patterns across Part 91, Part 135, and Part 121 operations.

Loading trend charts…

Browse the aviation graph

Move quickly by aircraft, airport, operator, and time with indexes built for research, not wandering.

Last Data Update

By Decade

By Month

Aircraft Manufacturer

More manufacturers

Airports

More airports

Operators

More operators

About

Aviation safety reports, made easier to study

NTSB Reports is an independent research and search tool for public aviation accident and incident records. It brings NTSB aviation reports, structured fields, docket files, extracted figures, photos, videos, and update history into one searchable interface.

The goal is practical safety education: make it faster to find relevant investigations, compare similar events, review factual records, and understand the evidence behind probable-cause and preliminary reports.

The investigative work and source records belong to the National Transportation Safety Board and the published investigation record. This site is not affiliated with or endorsed by the NTSB.

FAQs

NTSB Report

October 23, 2001 · North American SNJ-5 · N3246G

Mesa, AZ

Overview

Report Status
Final with probable cause
Event Type
Accident
Date
October 23, 2001
Injury Outcomes
No injuries (1 uninjured)
Location
Mesa, AZ
Aircraft
North American SNJ-5
Tail Number
N3246G
Injuries
None
Aircraft Damage
Substantial
NTSB Number
LAX02LA014

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 existing 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.

NTSB Probable Cause

The pilot's inadequate compensation for an existing crosswind condition, and failure to maintain directional control on the landing rollout.

Full 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.

Flight

Event TypeAccident
Event Time14:49 MST
Nearest AirportFalcon Fld (0nm N)
Runway22L
Runway Length5102 ft
Runway Width100 ft
Flight Plan FiledNone
Flight Plan ActivatedNo
Aircraft FireNo
Aircraft ExplosionNo

Aircraft

AircraftNorth American SNJ-5
Tail NumberN3246G
Aircraft CategoryAir
DamageSubstantial
Operating RulePart 91
Engines1
Engine TypeReciprocating
Engine DetailsPratt & Whitney · R-1340 · Reciprocating · 600
Seats2

People & Injuries

Injury SummaryNo injuries (1 uninjured)
Fatal0
Serious0
Minor0
Uninjured1
Total1
Crew 1Age 54 · First Class · None

Conditions

ConditionsVMC
LightDaylight
Wind250° @ 7 kt
Visibility10 sm
CeilingNone
Temperature / Dew Point41 C
Altimeter29.79 inHg
Observation Time21:56
Weather SourceWFAC

Appendix: Source Data