FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX84FUJ03 · Cessna T337E

1 Sept 1984 · Chandler, AZ, United States

Cessna T337E · Accident: overrun during takeoff

From Chandler, AZ to GUAYMAS

Report a problem

Event

NTSB case
LAX84FUJ03
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
0
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
General aviation
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

Cessna T337E

Aircraft type
Cessna 337
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
N1280M
Onboard fatalities
Unknown
Route
From Chandler, AZTo GUAYMAS
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 91: General Aviation
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
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
Overrun
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

  • Pilot in command › Aborted takeoff, delayed
  • Pilot in command › Airspeed(vlof), not attained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

THE PLT REPORTED THAT ON THE FIRST ATTEMPT TO ROTATE, THE STALL WARNING HORN ACTIVATED. THE PLT NOTICED THE REAR ENG IN AN OVERBOOST COND SO HE RETARDED THE THROTTLE COMPLETELY, THEN ADVANCED IT TO BELOW RED LINE. HE CONTINUED THE TAKEOFF AND ATTEMPTED TO ROTATE TWO MORE TIMES BEFORE HE ABORTED. HE RETARDED THE THROTTLES AND APPLIED FULL BRAKING BUT RAN OFF THE END OF THE RWY AND COLLIDED WITH A CONCRETE IRRIGATION DITCH. THE LANDING GEAR SEPARATED FROM THE AIRCRAFT. THE INVESTIGATION REVEALED THE ACFT WAS OVER MAX GROSS WT BY 311 LBS. THE PLT LOGGED 11 HRS TOTAL TIME AND 1 HR IN THE LAST 90 DAYS IN THE CESSNA T337E.THE OPERATING PROCEDURES IN THE OWNER'S MANUAL STATE THAT IF AN OVERBOOST OCCURS ON TAKEOFF, THE THROTTLE SHOULD BE RETARTED SLIGHTLY TO BELOW RED LINE. THE ENG MANUFACTURE INDICATED THAT THE RED LIMIT WILL BE EXCEEDED WHEN THE THROTTLES ARE ADVANCED FULL FWD AND THIS CONDITION IS NOT DETRIMENTAL TO THE ENG.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX84FUJ03
Event ID
20001214X41110
Case number
LAX84FUJ03
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. 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: 6fe1637b2b903e0c110eb6a4f7aa4766d4cb22592bc9b75e60d77c9219cc5838; retrieved 2026-09-21T17:28:16.035Z.