LAX03LA168 · Aero Commander 500B
Aero Commander 500B · Accident: in flight encounter with weather during initial climb
From Grand Canyon National Park Airport (GCN) to L67 · Rialto, CA
Event
- NTSB case
- LAX03LA168
- 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
- 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
Aero Commander 500B
- Aircraft type
- Aero Commander 500
- 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
- N64TS
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grand Canyon National Park Airport (GCN), Grand Canyon, AZTo L67 · Rialto, CA
- 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
- Initial climb
- 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
- In flight encounter with weather
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Tree(s)
- 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
- Aircraft performance, climb capability › Exceeded
- Weather condition › Sudden windshift
- Weather condition › Windshear
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 did not gain altitude after takeoff and collided with trees and terrain off the departure end of the runway. Prior to takeoff the pilot received a computerized weather briefing that showed generally good conditions. The tower controller cleared the pilot to taxi to the active runway (runway 21) and issued winds, which were 300 degrees at 10 knots, a direct crosswind. During the initial climb after liftoff, the pilot saw that the airplane had stopped climbing and he asked for and received the wind information again. With the airplane not climbing and headed directly for some trees, the pilot maneuvered the airplane towards a clearing but the left wing hit a tree and the airplane descended into the ground. The pilot reported no mechanical problems with the airframe and engines. The density altitude was calculated to be 9,481 feet. The aircraft's gross weight at the time of takeoff was 6,000 pounds. Review of the Airplane Flight Manual climb performance charts for that aircraft weight at the pressure altitude and reported outside air temperature discloses that the airplane should have had a positive rate of climb of about 1,100 feet per minute. The airport was equipped with a wind information recording system, which had four sensors. Three sensors recorded wind information at ground level only. They were placed, one each, at the approach, middle, and departure ends of the runway. Wind data was recorded every 10 seconds. The system does not have the capability to predict or warn of wind shear events. During the aircraft's departure, the approach end sensor recorded winds at 068 degrees at 1 knot; the middle sensor recorded winds at 293 degrees at 5 knots; and the departure sensor recorded winds at 302 degrees at 2 knots. At the next data sampling (10 seconds later), the departure end sensor recorded a wind increase of 10 knots, and the approach end recorded a wind shift from a headwind to a tailwind at 10 knots. A full analysis of the weather conditions indicated that due to developing convection over the runway the airplane likely encountered a wind shear (increasing tailwind) event that seriously degraded the takeoff and climb performance.
Probable cause
the pilot's encounter with a wind shear just after liftoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX03LA168
- Event ID
- 20030605X00802
- Case number
- LAX03LA168
- 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: local date, investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 2003-05-29.
- API snapshot SHA-256: 8fb3f7b34117c064fa2e2bda1a8318ce55fb2240eed0ec40fc7f8c1a5004e5c4; retrieved 2026-09-21T09:27:47.710Z.