Date: 201707
Local time of day: 1801-2400
Location: ORD.Airport, IL
Flight conditions: VMC
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ORD
ATC / advisory: TRACON C90
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Flight was uneventful from takeoff to beginning of descent. It was the Captain's leg and he briefed a visual approach to Rwy 28C backed up by the ILS. This was what we were expecting based on Weather and direction of flight. I believe we were on the BENKY4 RNAV arrival into ORD. Somewhere around our turn to downwind (maybe around 'PETAH'); ATC told us to expect Rwy 27L. The Captain briefed the backup information and I input the change into the FMS. I remember the Captain saying 'I think I read in the NOTAMS that the glideslope is out of service (OTS) for that runway'. This was confirmed when we heard approach tell another aircraft on 27L that it was OTS. Everything from this point on was uneventful until established on final other than specific speeds ATC was instructing us to fly. The swap to Tower went something like '[flight number] contact tower on 120.75; maintain 170 KIAS until TAFFS; contact Tower at TAFFS' (at this point we were about 5 miles from TAFFS). I'm not sure what all happened to lead to the event around TAFFS because I was heads down finishing [a] checklist and a lot was happening (contacting Tower; slowing to approach speed; finishing the checklist; etc). My assumption is that the Captain just put in too much of a descent rate with the AP (autopilot) at what would have been a normal glideslope intercept point. Tower contacted us and said 'low altitude alert check your altitude immediately' I looked up and saw 4 Red lights on the PAPI. At this point the Captain clicked off the AP and manually re-intercepted a proper visual glideslope. We were stable and checklist complete before 1000 and the landing was uneventful.Several factors contributed to this event. Late change of runway; glideslope being out of service; crunch point around TAFFS intersection compounded by ATC's request of speeds and radio communication; misapplication of AP descent rate at FAF; lack of crosscheck by the crew for adherence to recommended altitudes on the approach plate for 'LOC (GS out)'. Biggest thing would have been to brief the planned descent rate used by the AP based on the glideslope being out. Briefing and delegating adherence to the Recommended Altitudes for a LOC (GS out) approach. Anticipation of the crunch point around normal glideslope intercept and possibly an early slow/configuration to be stable at the point prior to intercepting a 3 deg glide path. AP usage and calculated descent rates for LOC approach. Cross-checking and communication by the FO for deviations based on those Recommended Altitudes.




Synopsis: Air carrier First Officer reported ORD Tower issued a low altitude alert to them when they got low on a localizer only approach to Runway 27L.