# NTSB LAX02LA084: Cessna 172S, N299ME, Glendale, AZ, February 13, 2002

- Type: NTSB accident investigation
- Classification: Accident · No injuries · Limited investigation · Final report
- Date: February 13, 2002, 09:17 local (16:17 UTC)
- Place: Glendale, AZ
- Coordinates: 33.529975, -112.309555 (estimated)
- Nearby events: https://openairdocs.org/map.md?lat=33.5300&lon=-112.3096&mi=10
- Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping)
- Highest injury: No injuries
- Injuries: 4 uninjured
- Status: Completed, report October 24, 2002
- Report: Approved by Office Director
- Parties: FAA-WP-FSDO
- NTSB case key (mKey): 54194
- NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX02LA084
- NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54194/pdf
- NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54194
- Page: https://openairdocs.org/ntsb/LAX02LA084

## Probable cause (aircraft 2)

The pilot of the landing airplane failed to maintain directional control resulting in the on-ground collission.

## Probable cause (aircraft 1)

The pilot of the landing airplane failed to maintain directional control resulting in the on-ground collission.

## Sequence of events

In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf).

- Loss of control - on ground/water, landing - roll
  - directional control - not maintained, pilot in command (cause)
- Collision between aircraft (other than midair), landing - roll
  - object - aircraft moving on ground (contributing factor)
- Collision between aircraft (other than midair), taxi - to takeoff
  - evasive maneuver - attempted, pilot in command(cfi)
  - object - aircraft moving on ground (contributing factor)
  - directional control - not maintained, pilot of other aircraft (cause)

## Analysis (aircraft 2)

A Cessna 172S veered off runway 01 during landing and collided on the ground with a taxiing Cessna 172N.  The pilot of the landing 172S completed air work in the local practice area and returned for landing.  On his first touch-and-go, the airplane veered to the left, but he regained directional control and took off.  On the second touch-and-go, the airplane veered to the left again, but he could not recover.  The airplane exited the runway about midfield between a taxiway and the high-speed taxiway.  It crossed a gravel area between the runway and a parallel taxiway.  The instructor and student in the taxiing 172N were taxiing to runway 01 via taxiway alpha.  They saw the landing 172S bounce and veer towards the hangars.  They stopped and thought the 172S would pass in front of them.  However, the landing 172S turned directly towards them.  They tried to turn away, but did not have enough time to avoid the collision.  The airplanes converged from opposite directions so that the entire leading edge of the left wing of the landing 172S collided with the entire leading edge of the left wing of the taxiing 172N.  The left wing tips contacted the left wing roots of the opposing airplane.

## Analysis (aircraft 1)

A Cessna 172S veered off runway 01 during landing and collided on the ground with a taxiing Cessna 172N.  The pilot of the landing 172S completed air work in the local practice area and returned for landing.  On his first touch-and-go, the airplane veered to the left, but he regained directional control and took off.  On the second touch-and-go, the airplane veered to the left again, but he could not recover.  The airplane exited the runway about midfield between a taxiway and the high-speed taxiway.  It crossed a gravel area between the runway and a parallel taxiway.  The instructor and student in the taxiing 172N were taxiing to runway 01 via taxiway alpha.  They saw the landing 172S bounce and veer towards the hangars.  They stopped and thought the 172S would pass in front of them.  However, the landing 172S turned directly towards them.  They tried to turn away, but did not have enough time to avoid the collision.  The airplanes converged from opposite directions so that the entire leading edge of the left wing of the landing 172S collided with the entire leading edge of the left wing of the taxiing 172N.  The left wing tips contacted the left wing roots of the opposing airplane.

## Factual narrative (aircraft 2)

On February 13, 2002, at 0917 mountain standard time, a Cessna 172S, N299ME, veered off runway 01 during landing and collided on the ground with a taxiing Cessna 172N, N739NS, at Glendale Municipal Airport, Glendale, Arizona.  Glendale Aviation LLC was operating both rental airplanes under the provisions of 14 CFR Part 91.  The private pilot and one passenger in the landing 172S were not injured; the airplane sustained substantial damage.  The certified flight instructor and student pilot in the taxiing 172N were not injured; the airplane sustained substantial damage.  The landing 172S departed Glendale on a personal local flight about 0815.  Visual meteorological conditions prevailed, and no flight plan had been filed for either airplane.

The pilot of the landing 172S submitted a written statement.  The pilot said he completed air work in the local practice area and returned for landing.  On his first touch-and-go, the airplane veered to the left, but he regained directional control and took off.  On the second touch-and-go, the airplane veered to the left again, but he could not recover.  The airplane exited the runway about midfield between a taxiway and the high-speed taxiway.  It crossed a gravel area between the runway and a parallel taxiway.

The instructor and student in the taxiing 172N submitted a written statement.  They were taxiing to runway 01 via taxiway alpha.  They saw the landing 172S bounce and veer towards the hangars.  They stopped and thought the 172S would pass in front of them.  However, the landing 172S turned directly towards them.  They tried to turn away, but did not have enough time to avoid the collision.

The airplanes converged from opposite directions so that the entire leading edge of the left wing of the landing 172S collided with the entire leading edge of the left wing of the taxiing 172N.  The left wing tips contacted the left wing roots of the opposing airplane.  Both airplanes sustained substantial damage to the wings and fuselage.

## Factual narrative (aircraft 1)

On February 13, 2002, at 0917 mountain standard time, a Cessna 172S, N299ME, veered off runway 01 during landing and collided on the ground with a taxiing Cessna 172N, N739NS, at Glendale Municipal Airport, Glendale, Arizona.  Glendale Aviation LLC was operating both rental airplanes under the provisions of 14 CFR Part 91.  The private pilot and one passenger in the landing 172S were not injured; the airplane sustained substantial damage.  The certified flight instructor and student pilot in the taxiing 172N were not injured; the airplane sustained substantial damage.  The landing 172S departed Glendale on a personal local flight about 0815.  Visual meteorological conditions prevailed, and no flight plan had been filed for either airplane.

The pilot of the landing 172S submitted a written statement.  The pilot said he completed air work in the local practice area and returned for landing.  On his first touch-and-go, the airplane veered to the left, but he regained directional control and took off.  On the second touch-and-go, the airplane veered to the left again, but he could not recover.  The airplane exited the runway about midfield between a taxiway and the high-speed taxiway.  It crossed a gravel area between the runway and a parallel taxiway.

The instructor and student in the taxiing 172N submitted a written statement.  They were taxiing to runway 01 via taxiway alpha.  They saw the landing 172S bounce and veer towards the hangars.  They stopped and thought the 172S would pass in front of them.  However, the landing 172S turned directly towards them.  They tried to turn away, but did not have enough time to avoid the collision.

The airplanes converged from opposite directions so that the entire leading edge of the left wing of the landing 172S collided with the entire leading edge of the left wing of the taxiing 172N.  The left wing tips contacted the left wing roots of the opposing airplane.  Both airplanes sustained substantial damage to the wings and fuselage.

## Aircraft 1

- Registration: [N299ME](https://openairdocs.org/deregistered/N299ME-2004-11-24), registration cancelled 2004-11-24, S/N 172S8558, built 2000 (OpenAirDocs)
- Reported make and model: Cessna 172S
- Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs)
- Registry engine: [Lycoming I0360 series](https://openairdocs.org/engine/lycoming-i0360-series) (registry code 41515, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 172S8558
- Airframe hours: 790
- Engines: Lycoming IO-360L2A 180 horsepower reciprocating
- Damage: Substantial damage
- Flight: Personal, Part 91
- Operator: Glendale Aviation LLC
- Registered owner: Desert Wind Aviation
- Airworthiness certificate: Standard, Normal
- Last inspection: Continuous airworthiness, January 23, 2002, 8 hours before
- Departed: GEU, GLENDALE
- Airport: GEU, Glendale, runway 01, 5,350 × 75 ft, asphalt

## Aircraft 2

- Registration: [N739NS](https://openairdocs.org/deregistered/N739NS-2013-05-07), registration cancelled 2013-05-07, S/N 17270679, built 1978 (OpenAirDocs)
- Reported make and model: Cessna 172N
- Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs)
- Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs)
- Category: Airplane
- Serial number: 17270679
- Airframe hours: 5683
- Engines: Lycoming O-320D2G 160 horsepower reciprocating
- Damage: Substantial damage
- Flight: Instructional, Part 91
- Registered owner: Glendale Aviation LLC
- Airworthiness certificate: Standard, Normal
- Last inspection: 100 hour, January 19, 2002, 44 hours before
- Departed: GEU, GLENDALE, AZ
- Airport: GEU, Glendale

## Flight crew

As NTSB recorded them. NTSB leaves out names.

- Pilot, aircraft N299ME; age 64; injuries: none; private; airplane ratings: single-engine land; medical: class 3, valid medical--w/ waivers/lim; last flight review March 2, 2002; seat: left; flight hours: 151 total, 17 in this make and model, 41 as pilot in command, 3 in the last 90 days
- Flight instructor, aircraft N739NS; age 36; injuries: none; commercial; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2, valid medical--no waivers/lim.; last flight review February 4, 2002; seat: right; flight hours: 1,800 total, 600 in this make and model, 1,686 as pilot in command
- Student pilot, aircraft N739NS; age 23; injuries: none; student; medical: class 2, valid medical--no waivers/lim.; seat: left; flight hours: 32 total, 32 in this make and model

## Weather

- Conditions: Visual (VMC), Day
- Wind: 0° at 0 knots
- Visibility: 20 statute miles
- Lowest ceiling: none
- Temperature: 52 °F
- Altimeter: 30.11 inHg
- Observed at: GEU

## FAA reports on this event (2)

The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs).

- [Accident 20020213001139A](https://openairdocs.org/incident/20020213001139A), Feb 13, 2002: Cessna 172S, Glendale, AZ, Substantial damage. (.19) On February 13, 2002, at 0917 mountain standard time, a Cessna 172S, N299ME, veered off runway 01 during landing and collided on the ground with a…
- [Accident 20020213001189A](https://openairdocs.org/incident/20020213001189A), Feb 13, 2002: Cessna 172N, Glendale, AZ, Substantial damage. (.19) On February 13, 2002, at 0917 mountain standard time, a Cessna 172S, N299ME, veered off runway 01 during landing and collided on the ground with a…

## Docket (3 files)

The files NTSB released with the investigation on September 11, 2002, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54194. 732 KB in all.

- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1, N739NS (item 1, .PDF, 352 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40387334&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1,%20N739NS-Redacted.PDF
- Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1, N299ME (item 2, .PDF, 344 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40387335&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1,%20N299ME-Redacted.PDF
- Supplement S (item 3, .PDF, 36 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40164755&FileExtension=.PDF&FileName=Supplement%20S-Master.PDF

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.

---
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.
