2002 United States airtanker crashes
(USDA) Forestry Service Lockheed C-130A · Structural failure, wing detachment
From Minden-Tahoe Airport (MEV) to Minden-Tahoe Airport (MEV)
Event
- NTSB case
- LAX02GA201
- 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
- Event fatalities
- 3 · all aircraft and ground
- Ground fatalities
- Unknown
- Occupants
- 3
- Survivors
- 0
- InjuriesFatal: death within 30 days. Serious: over 48 hours in hospital within a week, most broken bones, severe bleeding, nerve or organ damage, or serious burns. Minor: anything less. Glossary
- 0 serious · 0 minor (NTSB)
- 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
- Government
- 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
Lockheed C-130A
- Aircraft type
- Lockheed C-130
- 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
- N130HP
- Operator
- USDA - Forestry Service
- Onboard fatalities
- Unknown
- Route
- From Minden-Tahoe Airport (MEV), Minden, NVTo Minden-Tahoe Airport (MEV)
- 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
- Public Aircraft
- 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
- Maneuvering · aerial application
- 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
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Wing, skin › Fatigue
- Wing, spar › Fatigue
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
From the Wikipedia article
In June and July 2002, two large airtankers – a Lockheed C-130 Hercules and a Consolidated PB4Y-2 Privateer – crashed about a month apart while performing aerial firefighting operations. These crashes prompted a review of the maintenance and use of the entire U.S. large airtanker fleet. Ultimately, the whole fleet (33 aircraft in all) was grounded, dramatically reducing the resources available to fight major wildfires. Both aircraft were owned by Hawkins & Powers Aviation of Greybull, Wyoming and operated under contract to the United States Forest Service (USFS). The crashes occurred in one of the worst fire seasons in the last half century, one in which 73,000 fires burned 7.2 e6acre of land.
Text from the Wikipedia article “2002 United States airtanker crashes” (revision 1368921121, retrieved 2026-09-18) by its authors, under CC BY-SA 4.0. Extracted as plain text: references, tables, images and some sections are left out. Read the article
NTSB narrative
The airplane was making a fire retardant drop over a mountain drainage valley when the wings separated from the fuselage. A videotape of the accident sequence showed the airplane as it flew down the valley and proceeded to make a fire retardant drop. When the drop was almost completed, the airplane's nose began moving up, and the airplane started to arrest its descent and level out. The nose of the airplane continued to rise, and the airplane's wings folded upward until they detached from the fuselage at the center wing box beam-to-fuselage attachment location. Close examination of the video revealed that the right wing folded upward first, followed by the left wing about 1 second later. Metallurgical examination of the center wing box lower skin revealed a 12-inch long fatigue crack on the lower surface of the right wing beneath the forward doubler, with two separate fatigue crack initiation sites at stringer attachment rivet holes (which join the external doubler and the internal stringers to the lower skin panel). The cracks from both initiation sites eventually linked up to create a single crack. The portion of the wing skin containing the fatigue crack was covered by a manufacturer-installed doubler, which would have hidden the crack from view and, therefore, prevented detection of the crack from a visual inspection of the exterior of the airplane. The investigation found that the airplane was probably operated within the maximum takeoff gross weight limits specified in the airplane flight manual. The airplane was delivered new to the U.S. Air Force (USAF) in 1957 and was retired from military service in 1978. The U.S. Forest Service (USFS) acquired it from the USAF in 1988 for use as a fire suppression tanker. Between 1978 and 1988, it was kept in a desert storage facility. It was transferred to a civilian contractor for firefighting operations and modified for that role, then sold to a Part 135 operator. The airplane was certificated by the FAA in the restricted category under a type certificate held by the USFS. A Lockheed study concluded that firefighting missions were substantially more severe than typical military logistics operations and aircraft operated in this role would require inspection intervals as much as 12 times more frequently than typical military transport usage for meeting damage tolerance requirements. Concerning the detectability of the cracks, Lockheed reported that nondestructive x-ray inspection methods in current industry and military depot level maintenance processes could have detected, with high confidence, the fatigue cracks when they were 0.50 to 0.75 inch long. Inspection intervals appropriate for this detectable crack size can be determined from a damage tolerance crack growth analysis; however, this requires an extensive knowledge of the operational loads environment and internal stresses of the C-130A wing such as would be found in a military depot level maintenance program. The operating limitations accompanying the restricted certificate specified that it be flown and maintained in accordance with the then-current (1988) USAF technical orders for the C-130A. The USAF depot level maintenance program was not included in the maintenance technical orders and was not individually specified on the certificate's operating limitations. The limitations letter did not specify compliance with USAF maintenance program modifications/amendments in technical orders issued after 1988. The operator devised a maintenance and inspection program based on the specified USAF maintenance technical order but did not develop a depot level inspection requirement to ensure continued long-term airworthiness and damage tolerance that would account for the stresses on the airplane resulting from its new firefighting role and the increasing age of the airplanes. Investigation found that there are five separate FAA-issued type certificates owned by five separate firms for the C-130As used as tankers. Although the five certificates have similar maintenance requirements, none are standardized, there is no depot level maintenance program specified for any of them, and none require full compliance with all military airworthiness technical orders. In 1991, the Department of Interior (DOI) began to doubt the continued airworthiness of the C-130A firefighting tanker fleet and was specifically concerned that the lack of a depot level maintenance program or any requirement for compliance with all military airworthiness technical orders could compromise the safety of the airplane. The DOI asked the FAA to standardize the type certificate for the C-130A and mandate improvements in the maintenance and inspection requirements. In a written opinion, the USAF agreed and urged the FAA to mandate that operators establish a depot level type continuing airworthiness program for the airplane and mandate compliance with all technical orders. In a series of meetings held in 1993, FAA management internally agreed that the DOI and USAF positions held merit and began to develop requirements. In late 1993, in a meeting between the FAA, DOI, USFS, and the airplane operators, the USFS and the operators objected to the idea of depot level maintenance programs and full compliance with all technical orders on the basis of the potential economic impact of these requirements. As of the time of the accident, the FAA had not standardized the existing five type certificates nor had they imposed any additional maintenance or inspection program requirements.
Probable cause
the inflight failure of the right wing due to fatigue cracking in the center wing lower skin and underlying structural members. A factor contributing to the accident was inadequate maintenance procedures to detect fatigue cracking.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
Wikipedia article: 2002 United States airtanker crashes
- Revision
- 1368921121 · 2026-08-11 · retrieved 2026-09-18
- Wikidata
- Q4600673
- Licence
- Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record LAX02GA201
- Event ID
- 20020621X00954
- Case number
- LAX02GA201
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Where each value comes from
- Record
- Wikipedia article "2002 United States airtanker crashes" (page 13468770, revision 1368921121); merged with NTSB case LAX02GA201 (events / aircraft)
- Date
- NTSB record LAX02GA201: NTSB narrative opening date, consistent with the API date and time (local date)
- Place and country
- Wikipedia infobox: site; country from NTSB record LAX02GA201
- Map position
- NTSB record LAX02GA201: NTSB API eventLatitude/eventLongitude
- Aircraft, operator and route
- NTSB record LAX02GA201: aircraft; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
- Operation
- NTSB record LAX02GA201: operated under Public Aircraft
- Fatalities
- NTSB record LAX02GA201: NTSB API totalFatal
- Ground fatalities
- NTSB record LAX02GA201: events.inj_f_grnd
- Summary
- Wikipedia infobox: summary
Source notes (3)
- One occurrence in two sources, merged: the Wikipedia article "2002 United States airtanker crashes" and NTSB case LAX02GA201, matched by the same aircraft registration and date. For this US event the NTSB's values are used where the two differ; each value names its source.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. 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.