FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

C.A.T.S. Tours Fairchild SA227-AC accident

29 Sept 2002 · Hawthorne, CA, United States

Fairchild SA227-AC · Accident: loss of control on ground/water during takeoff

From Jack Northrop Field Hawthorne Municipal Airport (HHR) to Grand Canyon National Park Airport (GCN)

Report a problem

Event

NTSB case
LAX02FA300
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
Charter & commuter
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Fairchild SA227-AC

Aircraft type
Fairchild SA227
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N343AE
Onboard fatalities
Unknown
Route
From Jack Northrop Field Hawthorne Municipal Airport (HHR), Hawthorne, CATo Grand Canyon National Park Airport (GCN), Grand Canyon, AZ
Aircraft age
Not recorded
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 135: Air Taxi & Commuter
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff · roll/run
First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control on ground/water
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Flightcrew › Procedures/directives, not complied with
  • Pilot in command › Checklist, not followed
  • Pilot in command › Directional control, not maintained
  • Pilot in command › Ground loop/swerve, not corrected
  • Propeller system/accessories, pitch change mech › Not engaged

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane veered off the runway during a rejected takeoff, overran an airport sign, and impacted a hangar. The captain stated that during the after start checklist he moved the power levers to disengage the start locks on the propellers. Post accident examination found that the left propeller was still in the start lock position, while the right propeller was in the normal operating range. The captain was the pilot flying (PF) and the second-in-command (SIC) was the nonflying pilot (NFP). After receiving their clearance, the PF taxied onto the runway and initiated the takeoff sequence. The SIC did not set and monitor the engine power during takeoff, as required by the company procedures. During the takeoff acceleration when the speed was between 40 and 60 knots, the captain released the nose gear steering control switch as the rudder became aerodynamically effective. When the switch was released, the airplane began immediately veering left due to the asymmetrical thrust between the left and right engine propellers. The PIC did not advise the SIC that he had lost directional control and was aborting the takeoff, as required by company procedures. The distance between where the PIC reported that he began the takeoff roll and where the first tire marks became apparent was about 630 feet, and the distance between where the marks first became apparent and where the airplane's left main landing gear tire marks exited the left side of the runway was about 220 feet. Thereafter, marks (depressions in the dirt) were noted for a 108-foot-long distance in the field located adjacent to the runway. Medium intensity tire tread marks were apparent on the parallel taxiway and the adjacent vehicle service road. These tread marks, over a 332-foot-long distance, led directly to progressively more pronounced marks and rubber transfer, and to the accident airplane's landing gear tires. Based on an examination of tire tracks and skid marks, the PIC did not reject the takeoff until the airplane approached the runway's edge, and was continuing its divergent track away from the runway's centerline. The airplane rolled on the runway through the dirt median and across a taxiway for 850 feet prior to the PIC applying moderate brakes, and evidence of heavier brake application was apparent only a few hundred feet from the impacted hangar. No evidence of preimpact mechanical failures or malfunctions was found with the propeller assemblies, nose wheel steering mechanism, or brakes.

Probable cause

The pilot-in-command's failure to maintain directional control during the rejected takeoff. The loss of directional control was caused by the crew's failure to follow prescribed pretakeoff and takeoff checklist procedures to ensure the both propellers were out of the start locks. Contributing factors were the failure of the crew to follow normal company procedures during takeoff, the failure of the flightcrew to recognize an abnormal propeller condition during takeoff, and a lack of crew coordination in performing a rejected takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX02FA300
Event ID
20021007X05286
Case number
LAX02FA300
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 6059c56a2c9b098e3a9c38e537790ba3cb618d8b2255ae8e487072f508feb2cc; retrieved 2026-09-18T15:57:54.560Z.