KR Five-Four
KR Five-Four
Production information

Coalition of Ordered Governments

Product line

King Raven

Technical specifications
Maximum speed

180 kph

Engine unit(s)

Coaxial Rotors



  • Frontal Machine Gun
  • Chain Gun attachments on the sides
  • One pilot
  • One co-pilot
Cargo capacity

12 Gears[1]

  • Assault
  • Carrier[2]
  • Troop Transport

1st Frost, 14 A.E.[3]

"This is KR Five-Four! I'm hit, I'm..."
— The pilot of KR Five-Four, as it goes down in the Ilima sinkhole

KR Five-Four was a King Raven unit in the Coalition of Ordered Governments Air Corps that took part in Operation: Hollow Storm.


KR Five-FourGoingDown

KR Five-Four going down in the Ilima sinkhole.

Operation: Hollow StormEdit

"This is KR Five-Four. Raven down. I've got Charlie-Nine; Locust approaching our position. Requesting assistance."
— The pilot of KR Five-Four, after crashing in the Ilima sinkhole

Fourteen years after Emergence Day, during the Battle of Ilima, KR Five-Four was shot down while ferrying Charlie-Nine, and crash-landed in the Ilima sinkhole. The pilot survived and was able to pop green smoke to mark his position, and commed to warn that the crash site was under attack. Locust forces overwhelmed Five-Four's crash site and killed the survivors before Delta-One could arrive. The Locust then proceeded to use the crash site as a trap for Delta and nearly overwhelmed them before Pvt. Augustus Cole rescued them.[4]

Known CrewEdit

  • Unidentified Male Pilot: This pilot was killed during the Battle of Ilima when KR Five-Four went down in the Ilima sinkhole, and the crash site was overwhelmed by Locust.



  1. Gears of War: Destroyed Beauty
  2. Gears of War 2: Act 2: Denizens: Intestinal Fortitude
  3. Gears of War: Jacinto's Remnant pg 3
  4. Gears of War 2: Act 2: Denizens: Sinking Feeling

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.