Date: 201811
Local time of day: 0001-0600
Location: ZZZZ.Airport, FO
Flight conditions: Mixed
Weather elements / visibility: Thunderstorm; Rain; 4
Light: Daylight
Aircraft: B767-300 and 300 ER
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Cargo / Freight / Delivery
Flight phase: Descent
ATC / advisory: Center ZZZZ
Aircraft component: Turbine Engine
Component problem: Failed
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying
Human factors: Time Pressure; Workload
Anomaly: Aircraft Equipment Problem Less Severe; Inflight Event / Encounter Weather / Turbulence
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Inflight Shutdown; Flight Crew Landed in Emergency Condition
Contributing factors: Aircraft; Weather
Primary problem: Aircraft

Narrative: Standard arrival procedures coming into ZZZZ; starting out on one of the STAR arrivals and then vectors to our final approach course. There was some deviation around CB's and rain showers coming towards the aerodrome with FEW at 600 feet; FEW at 1;700 feet CB; SCT 2;600 feet and BKN 13;000 feet. Winds were variable at 2 knots and the ATIS information was calling 7 KM vis with moderate rain. It was more like rain showers and we missed just about all the rain showers close to the airport. Upon being cleared for the approach and after joining final; Captain was hand flying the aircraft with the autopilot off and the auto throttles on and he noticed and verbalized some rudder oddity. There was a lot going on for me as I was talking to the Approach Controller; switching to Tower and configuring the airplane for the Captain as he verbalized the commands. He stated that the right engine was rolling back which it was and then he placed the Right Engine Start Selector to FLIGHT and moved the Right Thrust lever back slightly. I believe he clicked the Auto-throttle switch off at this point and I confirmed the Right Engine appeared to have flamed out and he commanded the flaps back to 20 degrees for landing and to reset the speed bug for a Flaps 20 SE approach; which I did. He was flying the airplane just fine; we had the runway in sight straight ahead and were established on the LOC and GS with the Gear Down and now Flaps 20. We did not feel rushed or that the outcome or our aircraft or approach to landing was in jeopardy so we continued. At this point; I believe I saw about 1;400 Feet AGL on the Radio Altimeter and we were configured for a simple and timely Flaps 20 SE landing. There was no traffic behind us or on the runway or anywhere near our landing runway so we did not verbalize any urgency or problem to the Tower. Captain just continued to fly the aircraft while I made the standard calls at 1;000 feet and again at 500 feet. The Landing Checklist may have been completed shortly after the 1;000 feet call and I don't remember which one of may have started the APU but I believe it was running prior to our touch down. I did query the Tower again on short final just to verify our landing clearance for [Runway] XXL and we did get the TOO LOW FLAPS EGPWS announcement due to our not overriding the system with the SE Flaps 20 Landing configuration. As soon as we heard the TOO LOW FLAPS we reverified the flap position and selected the Flaps EGPWS Override switch to Override and Captain landed the airplane uneventfully. All standard calls were made upon the landing roll out and we cleared the runway safely. After exiting; everything appeared to be normal other than the inoperative right engine; so we secured the right engine and followed our taxi clearance to parking at gate on the cargo apron via single engine taxi.




Synopsis: B767-300 First Officer reported a flameout of the Number 2 engine while on approach.