Aero Charter and Transport Cessna 310R accident
Cessna 310R · Accident: on ground/water collision with object while taxiing
From Kingman Airport (IGM) to Phoenix Sky Harbor International Airport (PHX)
Event
- NTSB case
- LAX08CA039
- 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
Cessna 310R
- Aircraft type
- Cessna 310
- 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
- N5499J
- Operator
- Aero Charter & Transport
- Onboard fatalities
- Unknown
- Route
- From Kingman Airport (IGM), Kingman, AZTo Phoenix Sky Harbor International Airport (PHX), Phoenix, 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
- Taxi · from runway
- 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
- On ground/water collision with object
- 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 › Clearance, not maintained
- Pilot in command › Taxispeed, excessive
- Pilot in command › Visual lookout, inadequate
- Pilot in command › Wrong taxi route, initiated
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
Following the nighttime landing during an air taxi cargo flight, the pilot exited the runway and headed toward the designated parking area. The pilot elected not to taxi via the marked taxiway/lead-in lines. After exiting the runway the pilot attempted to cut the corner off the route by heading along a diagonal course across the tarmac toward the parking area. Albeit a shorter route, the course across the non-movement parking area was not marked with taxiway/lead-in lines. En route, the pilot observed a parked airplane but failed to notice container carts on the tarmac, which were also located in the apron area. At 20 miles per hour and seconds before impacting one of the carts, the pilot applied brakes. The airplane skidded about 50 feet before overrunning a cart. The airplane's left main landing gear sheared off, and the left wing was bent as the airplane came to rest.
Probable cause
The pilot's selection of a wrong taxi route, inadequate visual lookout, failure to maintain separation from ground obstacles, and excessive taxi speed.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08CA039
- Event ID
- 20080207X00155
- Case number
- LAX08CA039
- 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 2007-12-19.
- API snapshot SHA-256: fd5bb70dd355dbd0e0a6ea94f56937f8e1210181655502e060bebdb0051f3b99; retrieved 2026-09-18T14:39:25.578Z.