FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

United Air Lines Flight 227

11 Nov 1965 · Salt Lake City International Airport, Salt Lake City, Utah, United States

Boeing B-727 · Crashed short of runway due to pilot error

From LaGuardia Airport (LGA) to San Francisco International Airport (SFO)

Report a problem

Event

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
Unknown
Event fatalities
43 · all aircraft and ground
Ground fatalities
0
Occupants
91
Survivors
48
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
35
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

Boeing B-727

Aircraft type
Boeing 727
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
N7030U
Onboard fatalities
Unknown
Route
From LaGuardia Airport (LGA)To San Francisco International Airport (SFO)
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 (scheduled domestic passenger service)
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
Approach
Defining eventThe 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
Undershoot
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

  • Miscellaneous acts, conditions › Action, lack of
  • Miscellaneous acts, conditions › Poorly planned approach
  • Pilot in command › Improper level off

Approximate · Coordinates from the Wikipedia article; not checked against an investigation report.

From the Wikipedia article

United Air Lines Flight 227 (N7030U), a scheduled passenger flight from LaGuardia Airport New York City to San Francisco International Airport, California, crashed short of the runway while attempting a scheduled landing at Salt Lake City International Airport, Utah, on Thursday, November 11, 1965.

Accident details

Flight 227, operated by a Boeing 727-22, departed LaGuardia Airport at 08:35 MST (10:35 EST) for San Francisco, California, with scheduled stops in Cleveland, Chicago, Denver, and Salt Lake City. The flight to Denver was routine. In Denver, a new flight crew took control of the plane: Captain Gale C. Kehmeier, First Officer Philip E. Spicer, and Second Officer Ronald R. Christensen. The flight took off from Denver at 16:54 MST, a few minutes after sunset.

During the flight, the first officer was flying the aircraft under the direction of the captain. At 17:35, it was cleared to descend to 16000 ft by the Salt Lake City Air Route Traffic Control Center.

At 17:47, now under the direction of terminal control, the plane was cleared to approach. At 17:48, in response to the controller's request for the plane's altitude, the pilot replied, "Okay, we've slowed to two fifty (250 kn) and we're at ten (10,000 ft), we have the runway (34L) in sight now, we'll cancel and standby with you for traffic." The plane began to descend, but its rate of descent was approximately 2300 ft per minute, nearly three times the recommended rate of descent.

At approximately 17:49:30, the plane passed the outer marker 5.7 mi from the runway threshold at approximately 8200 ft, over 2000 ft above the normal glideslope. The elevation of the Salt Lake City airport is 4227 ft above sea level.

At approximately 17:51, one minute prior to impact, the plane passed 6300 ft; it was still 1300 ft above the normal glideslope, and still descending at 2300 ft per minute. Around this time, the first officer reached forward to advance the thrust levers to increase thrust, but the captain brushed his hand aside and said, "Not yet."

At thirty seconds prior to impact, the plane was 1000 ft above and 1.25 mi from the runway. The captain indicated in post-crash interviews that at this point, he moved the thrust levers to the takeoff power position, but the engines failed to respond properly. However, both the testimonies of the other members of the flight crew and the data from the flight data recorder (FDR) indicate that the attempt to add power occurred only about ten seconds before impact.

At 17:52, the plane struck the ground 335 ft short of the runway, then slid 2838 ft. The separation of the landing gear and the No. 1 engine was the result of impact loading in excess of their design structural strength. The failure of the landing gear caused the rupture of fuel lines in the fuselage. The resulting fire, rather than the impact of the crash, accounted for all 43 fatalities. The incident occurred approximately forty minutes after sunset.

The Boeing aircraft had been delivered to United seven months earlier on April 7, 1965, and had less than 1,800 hours of flight time.

Investigation and cause

Investigation conclusions

This accident was blamed entirely on the bad judgment of the captain, Gale C. Kehmeier, for conducting the final approach from a position that was too high and too close to the airport to permit a descent at the normal and safe rate. He allowed the plane to fly the final approach segment (in visual conditions) at a descent rate of 2300 ft per minute (triple the safe descent rate). When the plane crossed the outer marker, which marks the final approach segment, it was 2000 ft too high.

The first officer, who was flying the aircraft under the captain's direction, attempted to add engine thrust. But the captain told him no and brushed his hands off the thrust levers. The captain took over the controls during the last few seconds, but it was too late to avoid crashing short of runway 34L. The plane impacted with a vertical acceleration force of 4.7-g.

That severe impact force broke off the left main landing gear, and caused the right main gear to thrust up through the fuselage, rupturing pressurized fuel lines in the process. While the plane continued to slide down the runway on the nose gear and fuselage, pressurized fuel ignited inside the cabin, turning an initially survivable crash into a fatal accident. Many of the 50 people who successfully evacuated were severely burned.

The CAB (Civil Aeronautics Board) accident investigation revealed that the captain had a checkered training history. He had failed his initial jet transition training course, and was returned to flying the DC-6. Later on, he also failed to pass a routine annual instrument proficiency check.

Text from the Wikipedia article “United Air Lines Flight 227” (revision 1361858634, 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 remarks

PILOT FAILED TO TAKE TIMELY ACTION TO ARREST AN EXCESSIVE DESCENT RATE DURING THE LANDING APPROACH

NTSB's remark from its 1962–1981 archive, as recorded (abbreviated, at most 98 characters): the archive has no narrative

Sources

Wikipedia article: United Air Lines Flight 227
Article
United Air Lines Flight 227
Revision
1361858634 · 2026-06-30 · retrieved 2026-09-18
Wikidata
Q7887343
Licence
Text CC BY-SA 4.0, by the article's authors; Wikidata CC0; town positions GeoNames (CC BY 4.0)
NTSB record
Event ID
19651111P005486
Case number
Unknown
Dataset
historical-pre1982
Source SHA-256
abe1a933b4b73583d61684309f7f0610c281e3c1de3537c6471bf2a98ba6481d
Where each value comes from
Record
Wikipedia article "United Air Lines Flight 227" (page 3595385, revision 1361858634); merged with NTSB case NTSB19651111P005486 (PRE1982 tblFirstHalf (one row per aircraft, grouped by date, place and time))
Date
NTSB record NTSB19651111P005486: PRE1982 DATE_OCCURRENCE
Place and country
Wikipedia infobox: site; country from NTSB record NTSB19651111P005486
Map position
Wikipedia: Wikipedia article coordinates
Aircraft, operator and route
NTSB record NTSB19651111P005486: PRE1982 REGIST_NO, ACFT_MAKE, ACFT_MODEL; gaps from Wikipedia infobox: aircraft type, registration, operator, origin and destination; route airports from the linked airport articles' Wikidata codes (OurAirports)
Operation
NTSB record NTSB19651111P005486: operated under Part 121: Air carrier (scheduled domestic passg.svc)
Fatalities
NTSB record NTSB19651111P005486: PRE1982 TOTAL_ABRD_FATAL of each aircraft, plus people on the ground and others outside the aircraft
Ground fatalities
NTSB record NTSB19651111P005486: events.inj_f_grnd
Summary
Wikipedia infobox: summary
Source notes (4)
  • One occurrence in two sources, merged: the Wikipedia article "United Air Lines Flight 227" and NTSB case NTSB19651111P005486, 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.
  • From NTSB's 1962-1981 archive (PRE1982), which holds at most a short remark (98 characters, abbreviated) instead of a narrative; the accident type, phase of flight, causes and conditions are NTSB's codes, decoded as the archive defines them.
  • Reviewed means this record passed the site's consistency check, not that it was checked against a narrative or report - there is none to check against.
  • The operation category is mapped from the archive's operator and operation codes and has not been reviewed.