# Incident 20151230021109I: Boeing 737-924ER, Chicago, IL, December 30, 2015

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: December 30, 2015, 07:43 local time
- Place: Chicago, IL
- Damage: No damage
- Phase of flight: Landing: Rollout
- Operating rules: Air carrier (Part 121)
- Operator: CALA
- Location: 41.8500° N, 87.6501° W: Placed by OpenAirDocs: center of Chicago, IL, within about 9 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=41.8500&lon=-87.6501&mi=10
- Aircraft: N67845, registered now (https://openairdocs.org/aircraft/N67845) (OpenAirDocs)
- Registry model: Boeing 737-924ER (registry code 13848A3, https://openairdocs.org/model/boeing-737-924er) (OpenAirDocs)
- Registry engine: CFM International CFM56-7B27E series (registry code 13078, https://openairdocs.org/engine/cfm-international-cfm56-7b27e-series) (OpenAirDocs)
- Reported make and model: BOEING 737-924ER
- People aboard: 172
- Fatal injuries: 0
- Other injuries: 0
- Pilot certificates: Airline transport, flight instructor
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20151230021109I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ON DECEMBER 30, 2015, @ APPROXIMATELY 07:43, UNITED AIRLINES FLIGHT 1977, A BOEING 737-924ER, ARRIVING ORD FROM SEA, LANDED ON RUNWAY 27R.  AFTER LANDING AND DURING THE ROLLOUT, THE AIRCRAFT OVERRAN THE RUNWAY, STRIKING SOME RUNWAY EDGE (END) LIGHTS AND CAME TO STOP IN THE RUNWAY OVERRUN AREA.  THE AIRCRAFT REMAINED ON THE HARD SURFACE IN THE OVERRUN AREA.   THE ONLY APPARENT DAMAGE TO THE AIRCRAFT WAS A CUT TO THE NUMBER 3 TIRE BUT UNKNOWN WHETHER OR NOT RUNWAY LIGHT FIXTURES CAUSED THIS.  THERE WERE NO INJURIES.

THE SURROUNDING OVERRUN AREA WAS DEICED AND THE AIRCRAFT WAS PUSHED BACK ONTO THE RUNWAY.  THE AIRCRAFT THEN TAXIED TO THE GATE UNDER ITS OWN POWER WITH PASSENGERS REMAINING ON BOARD.

AN INVESTIGATION REVEALED:

CREW RECEIVED BRAKING ACTION REPORT AS GOOD.

CREW SELECTED AUTOBRAKE POSITION 2.

AIRCRAFT LANDED AT THE NORMAL TOUCHDOWN ZONE.

CREW WAS LATE IN APPLYING REVERSE THRUST.

AIRCRAFT SPEEDBRAKES WERE POSSIBLY RETRACTED TOO EARLY.

WEATHER:  THE CONDITIONS WERE CHANGING RAPIDLY.  IN A MATTER OF 15 MINUTES, PRECIPITATION WHICH WAS REPORTED AS -SN WAS TURNED INTO A MIXTURE OF -SN AND - FREEZING DRIZZLE.

BOTH PILOTS SUBMITTED ASAP REPORTS AND THEY WILL BE HANDLED IN ACCORDANCE WITH THE CALA ASAP MOU.

ANY FURTHER INVESTIGATION, RECOMMENDATIONS AND CORRECTIVE ACTIONS ARE DEFERRED TO THE CALA CMO.

ON 3/10/16 GL-31 ATTENDED A SAFETY MEETING WITH UNITED AIRLINES, UNITED AIRLINES CMO, ORD ATC, AIRPORTS DIVISION, AND CITY OF CHICAGO AIRFIELD OPERATIONS.  DURING THIS MEETING, EVIDENCE WAS PRESENTED THAT REINFORCED WEATHER AND RUNWAY CONDITIONS AS THE CAUSAL FACTORS OF THIS INCIDENT.

DISCUSSIONS ALSO INCLUDED WAYS OF MITIGATING  FUTURE RISKS WITH BETTER COORDINATION BETWEEN AIR TRAFFIC AND AIRFIELD OPERATIONS AND THE AIRLINE.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

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