When Horde Siege extraction is blocked, check for an active invasion before treating the missing helicopter as a bug. In E-Day's October 7, 2026 launch baseline, invasions can temporarily block extraction until the large threat is defeated. Your squad must also finish its main objectives, clear the landing zone, and board in time. At least one member of your own squad must extract to complete the mission and retain mission-collected Weapon Parts.
The October 5 update fixes an extraction helicopter failing to appear during a Plaza Ruins Blitz mission. That is a specific confirmed correction, not proof that every extraction delay on every map is solved. Read the live objective and event state before leaving a productive run.
Identify what is blocking your exit
Start with the current objective text. A mission still asking for R.I.G. repairs has not reached the same state as one asking you to secure an extraction zone. Likewise, a map-wide invasion restriction is different from a helicopter failing to appear after the required conditions are satisfied.
| State you can observe | First action | Meaning for diagnosis |
|---|---|---|
| Main objective still active | Complete its remaining requirement | Extraction is not yet the final task |
| Invasion restriction active | Resolve the shared invasion | A blocked exit can be intentional |
| Landing zone remains hot | Clear threats and hold the zone | The Raven is not simply a taxi waiting anywhere |
| Raven has arrived | Board before the opportunity ends | Continuing optional activities risks missing the ride |
| Plaza Ruins Blitz helicopter absent | Confirm the October 5 update and current objective state | A specifically named launch issue was addressed |
| Everything appears complete but no progress follows | Preserve the objective and event state | An unresolved failure needs a precise report |
Check the state together. One squadmate watching an old marker while another follows the new objective can make a normal transition look stuck.
An invasion can block extraction by design
Invasion events bring large Locust threats onto the shared battlefield. All squads are notified, and the event can impose temporary modifiers affecting the whole map. The official examples include blocked extraction and disabled Supply Caches.
If the restriction is active, move from waiting for the helicopter to helping resolve the invasion. The official mode description recommends squads working together against these threats and their supporting units. A squad that contributes receives a portion of the rewards, but the immediate reason to participate is to remove the restriction preventing your exit.
Your own main mission can be complete while the invasion remains active. Do not use main-objective completion as proof that extraction must already be available. Check whether the event has ended and whether the restriction has been removed before returning to the landing zone.
A Corpser is one possible invasion threat. The launch fixes address blast charges delivered during its invasion failing to register. If the event's required action appears not to advance, record that specific stage instead of reporting only that the Raven never came.
Complete the R.I.G. task that remains
Most Horde Siege missions involve R.I.G.s, with different requirements depending on the objective. A battlefield that looks clear can still have an unfinished interaction or defense requirement.
For Secure, the task is to drive Locust forces from the assigned position. Calibrate asks you to defend a series of zones near the R.I.G. Repair requires collecting and reinstalling scattered components. Defend requires protecting the active device while it finishes its mapping sequence. Horde asks the squad to protect one R.I.G. through ten waves.
The Defend the R.I.G. objective and wave message show the main-task state to check before diagnosing an extraction problem.
Match your action to the current type. Killing visible enemies does not substitute for reinstalling a missing Repair component, and completing one calibration zone does not establish that the whole sequence is finished. Use the objective's visible progress rather than assuming the next stage should trigger because combat has become quiet.
The October 5 patch addresses certain Siege Blitz Secure objectives failing to complete. If your updated run still has a Secure task that does not advance, keep that symptom separate from a helicopter that never appears after extraction begins.
Follow the assigned landing zone
After your main objectives are completed, the game asks you to clear a landing zone and survive until the Raven arrives. Follow the current extraction marker and instruction. Do not remain at a previous defense position merely because that is where the squad spent most of the match.
The map can involve several squads with different main objectives. Your squad's assigned exit is the relevant one; another team's activity or helicopter should not be assumed to complete your mission.
Before moving, agree on the route and check who is still nearby. If the squad splits across the map, a player can be fighting at an old objective while others prepare to board. Call out the move and keep support available for the approach.
Once you reach the landing zone, identify cover and firing lanes that let you control the threats occupying it. This is a tactical recommendation rather than an assertion that a particular map position always works. The objective is to keep the assigned zone usable, not simply stand on its marker.
Clear the zone and keep it usable
An uncleared landing zone can prevent the Raven from completing extraction. Continue the required fight rather than assuming that main-mission completion ended enemy pressure. The final encounter is part of the run.
Watch the current threat direction and squad status. If a teammate is downed, decide whether the revive can be made without exposing the whole group. Use the available class abilities and equipment to keep the zone controlled, while preserving someone who can board.
Avoid turning the final fight into a late farming detour. Secondary objectives, COG Resupplies, and optional enemies can offer rewards, but they also demand time and can attract more Locust. A squad seeking retained Weapon Parts must finish extraction, not maximize the temporary tally at the cost of the ride.
A quiet-looking moment does not necessarily prove that every requirement is satisfied. Check the objective text for what remains. If the zone appears clear yet its state never changes, capture the scene and current instruction before deciding you have a technical blockage.
Board while the opportunity is available
When the Raven arrives, board in time. The official extraction description warns that failing to clear the area and board promptly can cost you the ride. A helicopter appearing is therefore only part of a successful exit.
Aim to get the full squad out, but remember the completion condition: technically, only one member of your own squad needs to make it out alive. That is a minimum survival requirement, not a recommendation to abandon teammates whenever boarding becomes possible.
If the situation is collapsing, communicate who can safely reach the helicopter. Keeping one player able to finish the mission can preserve the squad's completion when an attempt to save everyone would otherwise lead to a wipe. Make that decision from the actual fight and boarding opportunity rather than a rigid script.
Do not assume an extraction by another squad counts for yours. Twelve players share the map, but the mission and part-retention condition remain tied to your own squad.
Recover teammates without losing the final opportunity
Horde Siege lets killed players drop COG tags. Squadmates can collect those tags and deliver them to a Supply Cache to revive the player. Players from other squads can also collect tags for an instant revive.
Those systems can recover a run, but they do not remove the extraction requirement. Before leaving the zone to recover a teammate, check whether the Raven is arriving or boarding is already available. A rescue plan needs someone to keep the final objective from being lost.
If the entire squad is killed, a squad life is consumed. When all squad lives are exhausted, the mission fails and awards partial XP. That outcome should not be confused with successful extraction simply because the group earned experience afterward.
This is why an extraction diagnosis should include squad lives and the final outcome. A reward screen with some XP is not proof that the Raven requirement was met or that mission Weapon Parts should have been retained.
Apply the Plaza Ruins Blitz correction accurately
The October 5 patch specifically addresses the extraction helicopter failing to appear during a Plaza Ruins Blitz mission. If that matches the run you are investigating, install the update before another attempt and record the new result.
The correction does not name every map or playlist. Do not say that all missing-helicopter cases are fixed, and do not say the specific Plaza Ruins issue must still occur just because an older video shows it. Both claims overreach the patch scope.
For a post-update failure, confirm that the main objective ended, no invasion restriction remained, and the extraction instruction reached the appropriate stage. These observations do not prove a root cause, but they make your report more useful than “helicopter missing.”
If the problem is actually an unfinished Siege Blitz Secure objective, report that earlier stage. A mission prevented from reaching extraction is different from a mission that reaches extraction but never receives its helicopter.
Preserve the run before exiting a suspected blockage
Do not leave the mission as your first diagnostic step. Mission-collected Weapon Parts require successful squad extraction, and leaving can make the reward outcome harder to distinguish from the original issue.
Ask the group to compare the current objective and event restriction. Capture the map or objective display and note whether all players see the same state. If the run cannot advance despite the visible requirements being met, retain a short clip of the failed transition or absent helicopter.
There is no confirmed universal procedure that resets a stuck Horde extraction while guaranteeing rewards. Campaign checkpoint advice does not establish a reset option for a live Horde mission. Rejoining also should not be promised as a way to preserve every player's part tally after a disconnect.
Once the squad decides the run cannot proceed, record its final outcome honestly. If you do not know whether someone extracted after your exit, keep that uncertainty in the report.
Verify completion and report unresolved cases
After a successful boarding, check the results and retained Weapon Part balance. Separate mission parts, temporary Energy, temporary Squad Perks, Class XP, and Player XP. A normal end to temporary resources is not a missing extraction reward.
For an unresolved extraction failure, send Gears support the platform, update status, map, playlist, difficulty, main-objective state, invasion state, and what the Raven did. Add whether the issue affected the entire squad and whether anyone boarded.
Include the specific October 5 match if it applies: Plaza Ruins Blitz helicopter absent, or a Siege Blitz Secure objective not completing. The useful endpoint is a visibly completed squad extraction or a report that identifies the stage preventing it. Waiting at the landing zone without checking the event and objective state cannot distinguish an intentional restriction from a technical failure.