FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

American Trans Air Lockheed L1011-385-1 L1011-385- accident

9 May 2000 · MAUI, HI, United States

Lockheed L1011-385-1 L1011-385- · Accident: hard landing

From San Francisco International Airport (SFO) to Kahului International Airport (OGG)

Report a problem

Event

NTSB case
LAX00LA192
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
0
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
Airline
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 L1011-385-1 L1011-385-

Aircraft type
Lockheed L1011
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
N192AT
Onboard fatalities
Unknown
Route
From San Francisco International Airport (SFO), San Francisco, CATo Kahului International Airport (OGG)
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 121: Air Carrier
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
Landing · flare/touchdown
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
Hard landing
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 › Airspeed(vref), not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The scheduled airline Lockheed L-1011, sustained a tail strike during landing damaging the pressure bulkhead and several bell frames and stringers in the aft fuselage. According to the flight crew, the captain was landing on runway 2 using a flaps 42 (full down) setting. The ATIS was reporting winds from 060 degrees at 18 knots with gusts to 26 knots. Both pilots stated that as the airplane descended through 30 to 40 feet agl, a sudden high sink rate developed. The captain added power and pitched the nose up to arrest the rate of descent. All three crewmembers said that the landing was harder than normal, but none would classify as a "hard landing." According to the airport METAR, the winds at 0954 were from 060 degrees at 22 knots with higher gusts to 27 knots. Review of the high resolution ASOS wind data from a sensor near the touchdown zone for the runway disclosed no significant speed variations in either the head or crosswind components during the last 10 seconds of the approach. An FAA inspector entered the cockpit after the aircraft had been parked at the gate and observed the captain's airspeed indicator final approach speed bug setting at 142 knots. According to the airline's L-1011 Operations Manual, the inner bug is set to the final approach speed, which is Vref adjusted for 1/2 of the steady state wind plus all of the gust additive. The final bug setting cannot be less than Vref + 5, nor more than Vref + 20. For the aircraft's landing weight, the zero wind Vref was calculated at 138 knots, with a wind adjusted final approach speed of 150 knots. Read out of the Flight Data Recorder disclosed that in the 48 seconds prior to touchdown, the calibrated airspeed varied from 154 to 145 knots. In the 10 seconds prior to touchdown, the airspeed varied from 143 to 130 knots at wheel contact. In the 10-second period before touchdown, the airspeed decreased from 143 to 135 knots, then increased to 143 knots 3 seconds later, and then steadily decayed to the 130-knot value recorded at ground contact. At touchdown, the aircraft was 8 knots below the no-wind reference speed, and, 13 knots below the airline's minimum specified speed. The maximum pitch attitude value of 8.79 degrees aircraft nose up was 4 degrees less than the maximum allowable pitch attitude to prevent a tail strike. Teardown of the left and right main landing gear assemblies revealed no discrepancies, and no write-ups were found in the maintenance records for the previous 180 days.

Probable cause

The captain's failure to maintain the proper wind-adjusted Vref airspeed, by a margin which varied from 7 to 20 knots too slow, during the final 10 seconds of the approach prior to touchdown.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX00LA192
Event ID
20001212X21038
Case number
LAX00LA192
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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: investigation status. 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.
  • API snapshot SHA-256: a281291371b1e54398bb5842a7e4077f6d3d8f29fbbd301d85c072bbe340e30b; retrieved 2026-09-18T16:37:30.806Z.
  • The NTSB's operator name is blank for N192AT; the operator shown is the name the NTSB's other records give its FAA operator code, AMTA.