NTSB CAROL · Event
Event LAX03LA168
Registry · N64TS
FAA Aircraft Registry record.
Make / Model
CESSNA 172RG
Year of manufacture
1981 · 22 years old at event
Engine
LYCOMING O&VO-360 SER (180 hp)
Seats / Engines
4 seats · 1 engine
Last airworthiness date
19810918
ADS-B equipped
Yes — Mode-S A8649C
Registrant of record
LIPPINCOTT GEORGE T
Source: FAA Aircraft Registry (releasable master file).
Aircraft involved
Probable cause & findings
the pilot's encounter with a wind shear just after liftoff.
Factual narrative
On May 28, 2003, about 1720 mountain standard time, an Aero Commander 500B, N64TS, collided with trees and terrain shortly after takeoff from the Grand Canyon National Park (GCN), Grand Canyon, Arizona. The pilot operated the airplane under the provisions of 14 CFR Part 91. The airplane sustained substantial damage. The certificated airline transport pilot and one passenger sustained minor injuries, one passenger was seriously injured, and the third passenger was not injured. The personal cross-country flight was departing GCN en route to the Rialto Municipal (Miro Field) (L67), Rialto, California. Visual meteorological conditions prevailed, and a flight plan had not been filed. The wreckage was at 37 degrees 57 minutes north latitude and 112 degrees 08 minutes west longitude. The pilot and passengers arrived at the Grand Canyon on May 27, 2003, for an overnight stay, with a return to Rialto scheduled on the 28th. The pilot stated that they fueled at Rialto so they would not have to refuel at the Grand Canyon for the return trip. The pilot went into the local fixed base operator (FBO) and obtained a computerized weather briefing upon arriving at the airport about 1600 the day of the accident. He stated that at the time the weather was "generally good." After obtaining the weather briefing, he went out to the airplane to do a weight and balance calculation. During the previous evening/nighttime there had been an infestation of locusts, and the pilot wanted to check the screens inside the cowling to make sure there were no blockages. He opened the cowlings and a couple of moths flew out. No blockages were noted. While the pilot was performing the preflight, the passengers boarded the airplane. During the preflight he removed the gust locks, checked the oil, and rechecked the fuel, which he estimated to be 90 gallons. He also sumped the fuel drains, with no discrepancies encountered. After completing the preflight, he redistributed the passengers per the weight and balance calculations. The pilot started the airplane and obtained the current Automatic Terminal Information Service (ATIS) information. He then contacted ground control for taxi. He was cleared to taxi to the run-up area. While in the run-up area, he recalculated the density altitude because the temperature had dropped considerably due to weather. He then leaned the airplane for climb-out performance per the airplane flight manual. No mechanical anomalies were noted with the run-up. The pilot indicated that a Grand Canyon Airlines airplane had taken off to the south on runway 21 about 10 minutes prior to his departure. There were some thunderstorms in the vicinity of the airport; however, they were in the north and northeast sectors. The pilot reported that it was clear and there were blue skies to the south. The pilot was then cleared to taxi to the active runway (runway 21), and noted that it was sprinkling. He asked the tower for a wind check. A tower controller reported that the winds were from 300 degrees at 10 knots (a direct crosswind). The pilot applied full power for takeoff, and everything appeared normal. The airplane accelerated to 100 miles per hour (mph) and he rotated the airplane for takeoff. He initially noted a positive rate of climb, and retracted the landing gear. The airspeed did not increase or decrease from 100 mph, and the climb-out was very "slow." At that point, the airplane had already crossed over the boundary fence and it became clear that the climb rate was insufficient to avoid hitting the trees. He maneuvered the airplane to the right of the departure path towards a clearing. The tower controller also pointed out the clearing to the pilot. As he was navigating between two trees, the left wing struck a tree and the airplane made a decelerating turn to the left. The pilot stated that at no time did the stall warning horn activate. He kept the airplane as level as he could, with a slight nose high attitude. When the airplane struck the terrain, it was at a relatively flat attitude. The pilot and two passengers exited through the main door of the airplane, and one passenger kicked out the windshield. When they got out of the airplane, the pilot noted that fuel was spilling on the ground, but there was no fire. While waiting for rescue personnel, about 2-3 minutes later, it started to rain and then stopped. The pilot reported that the engines were functioning normally. The engines had been overhauled in 1996. He further stated that he believes the wind switched on him during takeoff; it went from a 90-degree crosswind to a tailwind. According to the local tower controller, he cleared the airplane for takeoff and issued a wind check. After takeoff, the pilot again asked for a wind check, which the controller issued and indicated that it was a direct crosswind. He observed that the airplane was not climbing, and advised him of a valley to the pilot's right. There were no further transmissions. Weather issued at the time of the accident by the tower controller were winds 300 degrees at 10 knots; few clouds at 12,000 feet above ground level; temperature 29 degrees Celsius; dew point 03 Celsius; and altimeter 30.29 inches of Mercury. According to the airport/facilities directory, the Grand Canyon National Park Airport is at an elevation of 6,609 feet. Utilizing a density altitude program, the National Transportation Safety Board investigator-in-charge calculated the density altitude as 9,481 feet, with a pressure altitude of 6,268 feet. According to the pilot, the aircraft 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.
METEOROLOGICAL INFORMATION
The Safety Board National Resource Specialist - Meteorology, obtained wind information from the Grand Canyon Airport. The airport has four wind sensors on the field, three of which record data. The sensors are placed, one each, at the approach end, middle, and departure end of runway 21. Wind data is recorded every 10 seconds. At the time (1720 MST), the accident airplane was departing the approach 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. During the time period of 1720-1723, the departure sensor recorded a wind increase to 10 knots. The middle sensor recorded a maximum headwind of 5 knots, and the approach end recorded a wind shift from a headwind (maximum 7 knots) to a tailwind at 10 knots. The specialist further noted that the developing convection over runway 21 likely resulted in a decreasing airplane performance wind shear (increasing tailwind) along the runway as the accident airplane departed. Surface weather data indicated a peak wind of 340 degrees true (326 magnetic) at 18 knots at 1725, which resulted in about an 8-knot tailwind and about a 16-knot crosswind to runway 21. According to the Federal Aviation Administration (FAA) a WME system was in place at the time of the accident. The WME provides immediate readings at ground level only, it does not have the capability to predict and warn of wind shear events. The FAA reported that on the day of the accident the WME was operational. 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. Source: NTSB Aviation Accident Database (Pre-2008 Archive) Retrieved: 2026-02-12
Verbatim from NTSB's published report. Source file
NTSB_2003_LAX03LA168.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (wind shear, stall, thunderstorm). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- NASA NTRS 2019 · Contractor Report (CR)
An Examination of Aviation Accidents Associated with Turbulence, Wind Shear and Thunderstorm
The focal point of the study reported here was the definition and examination of turbulence, wind shear and thunderstorm in relation to aviation accidents.
- NASA NTRS 2019 · Conference Paper
Optimal recovery from microburst wind shear
The flight path of a twin-jet transport aircraft is optimized in a microburst encounter during approach to landing. The objective is to execute an escape maneuver that maintains safe ground clearance …
- NASA NTRS 2019 · Reprint (Version printed in journal)
Evolution of downdrafts and rotation in an Illinois thunderstorm
Multiple-Doppler radar observations of a non-severe Illinois thunderstorm with nearly rectilinear vertical wind shear and storm motion related to the wind at a height of 2.5 km are discussed.
- NASA NTRS 2013 · Conference Paper
Optimal nonlinear estimation for aircraft flight control in wind shear
The most recent results in an ongoing research effort at Princeton in the area of flight dynamics in wind shear are described.
- NASA NTRS 2026 · Conference Paper
Computational Analysis of Steady State Aerodynamics of Transonic Truss-Braced Wing Configuration in Deep Stall
This study presents a computational investigation of steady state aerodynamics of the Subsonic Ultra-Green Aircraft Research (SUGAR) Transonic Truss-Braced Wing (TTBW) configuration over a wide range …
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
The Impact of Thunderstorms on Take-off Data in South Africa
Aviation and meteorology are entwined disciplines, as aviation occurs in the atmosphere. Prevailing weather conditions at take-off are of utmost importance to aviation.
Browse the full corpus — academia portal ↗