# Accident 20011023029639A: Namer SNJ5, Mesa, AZ, October 23, 2001

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 23, 2001, 14:49 local time
- Place: Mesa, AZ
- Airport: Falcon Field Airport
- Damage: Substantial damage
- Phase of flight: Roll-Out (Fixed Wing)
- Operating rules: General operating rules (Part 91)
- Location: 33.4500° N, 111.7167° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.4500&lon=-111.7167&mi=10
- Aircraft: N3246G, registered now (https://openairdocs.org/aircraft/N3246G) (OpenAirDocs)
- Registry model: North American SNJ-5 (registry code 6400418, https://openairdocs.org/model/north-american-snj-5) (OpenAirDocs)
- Registry engine: Pratt & Whitney R1340 series (registry code 52016, https://openairdocs.org/engine/pratt-whitney-r1340-series) (OpenAirDocs)
- Reported make and model: NAMER SNJ5
- Reported engine: PWA R1340*
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 6,000 total, 75 in this make and model
- NTSB investigation: [NTSB LAX02LA014](https://openairdocs.org/ntsb/LAX02LA014) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20011023029639A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) AIRMAN WAS PLANNING ON ACCOMPLISHING 3 TAKE OFFS AND LANDINGS TO A FULL STOP FOR CURRENCY. DURING FIRST FULL STOP LANDING, WITH AN APPROXIMATE 15 X-WIND, AIRMAN STATED HE TOUCHED DOWN ON THE CENTERLINE, FULL STALL LANDING AND ABOUT 3 TO 4 SECONDS AFTER TOUCHDOWN, THE AIRCRAFT STARTED TO VEER RIGHT. AIRMAN STATED HE APPLIED FULL LEFT RUDDER, AFT STICK AND RIGHT AILERON AND EVENTUALLY ADDED LEFT BRAKE TO ATTEMPT TO REGAIN DIRECTIONAL CONTROL. AIRCRAFT EXITED RIGHT SIDE OF RUNWAY AND RIGHT WING STRUCK A RUNWAY DISTANCE REMAINING MARKER. AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE AS SPAR DAMAGE OCCURRED. (.19) ON OCTOBER 23, 2001, AT 1458 HOURS 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, 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. (.4) 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. ACCORD                                 ING 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.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX02LA014](https://openairdocs.org/ntsb/LAX02LA014), Oct 23, 2001: North American SNJ-5 (N3246G), Mesa, AZ, substantial damage. Probable cause: The pilot's inadequate compensation for an existing crosswind condition, and failure to maintain directional control on the landing rollout.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.
