The Evasion Plan of Action, or EPA, is a pre-filled survival document that a military member completes before a high-risk mission. It tells recovery forces, in the member's own hand, where to go, how to signal, and what to avoid if that member becomes isolated behind enemy lines. Completion is typically mandatory in evasion-conduct training programs including the US Air Force's SERE course.

What it is: a written plan of action that a member prepares, carries, and executes after isolation. What it records: authentication data, planned evasion routes, contact points, and recovery criteria. Who reads it: recovery forces, who use the recorded content to verify the isolated member's identity and locate them. Trigger: the plan is opened only if you become isolated, meaning separated from your unit and no longer able to carry out the mission.

If you're researching what information the plan supplies to recovery forces, use that definition for the rest of this article.

Why the Plan Inverts Normal Escape Thinking

Conventional escape training teaches you to run, and most service members default to that instinct the moment contact is lost. The plan inverts that instinct by naming, in advance, the conditions under which you should stay put, hide, and wait for recovery instead of moving. Recalling the plan under stress is a failure case documented in evasion-conduct instruction.

Historical evidence supports the approach. During the Vietnam War, US aircrew who were shot down over North Vietnam frequently had little warning and no time to prepare a written plan. Once isolated, they were moved rapidly and faced immediate capture or evasion decisions. The survival, evasion, resistance, and escape training that grew out of that experience now requires members to complete evasive planning before departure, not improvise later.

Evasion survives on minutes. A member who tries to recall a route under fire loses time and focus, and every pause increases the chance of detection. A pre-written plan converts recall into execution.

Five Items You Write Before Isolation

Write all five items on a single card, laminate it, and carry it in a location where capture won't reach it easily. If a field can't be known before departure, mark it conditional and confirm it in the ready room. The Air Force Handbook 10-644, Survival, Evasion, and Recovery, published by the Department of the Air Force, lists the standard checklist items in its planning section.

1: Authentication data. Record the challenge and reply words plus one or two personal identifiers that only your recovery force knows. Date the entry, because authentication countersigns can change. A stale reply word is a failure case: you say the phrase, the recovery crew treats you as a trap, and extraction stalls. 2: Evasion route and destinations. Plot your planned route, at least one alternate, and the specific contact points where you'll stop moving and wait. Name the points precisely, using terrain or grid references, and include a holding period for each. 3: Signaling plan. Write your panel, flare, radio, and visual signal sequence, and the time windows when you'll show them. Recovery crews watch narrow windows, so your plan must name the times. 4: Recovery criteria. State the conditions under which you'll move toward recovery versus stay hidden, and how you'll verify a rescue element is genuine rather than a deception. 5: Capture criteria. Set the limits you'll follow if capture becomes likely, and the information you may release under duress. Leave blank any content your command hasn't authorized.

What Recovery Forces Pull From a Completed Plan

Recovery forces use four fields above all others: authentication data to confirm identity, your route to narrow the search area, your signaling plan to schedule observation, and your holding points to know where you'll stop. Everything else on the card supports those four. Reasons the plan matters, per the Air Force Handbook 10-644, include speeding recovery, reducing the recovery force's exposure, and preventing an isolated member from being mistaken for the enemy.

Authentication comes first because recovery is a two-way risk. A crew that extracts the wrong person, or flies into a trap, can lose the aircraft and its people. Your challenge and reply phrase lets the crew confirm you before they expose themselves. That's why authentication data sits at the top of the checklist.

Route and contact-point data compress the search. Without a route, a recovery force can only search where the radio or beacon puts you. With a route, they know where to look when the beacon fails or is unavailable. The holding period at each contact point matters just as much: it tells the crew how long you'll be at a location.

The signaling plan schedules observation. A recovery crew can't watch every window for days. Your plan gives them times and signal types, so they can lay a watch when you're likely to appear.

Building Your Route, Contact Points, and Holding Times

Start with the map and build the plan around terrain, not around hope. Mark your planned evasion route, one alternate, and named contact points where you'll stop and hold. Give each contact point a holding period, such as a set number of days, so the recovery force knows how long you'll be there. Write the route and the holding times on your card. According to the Air Force Handbook 10-644, a destination and an alternate are both required elements.

Contact point choice is where the plan earns its keep. Pick points you can reach on foot, with cover, and near terrain that recovery aircraft or ground teams can use. Isolated desert terrain offers few landmarks, so a named wash or ridge junction beats "open ground near the road."

Holding periods create a schedule for the recovery force. If you plan to hold at a point for a set number of days, the crew knows to watch that area for that window. If you never arrive, they know to search the route between points.

Write the plan before you're isolated, set a review cadence, and keep the date current. A route drawn from a map two seasons old may no longer match the ground.

The Authentication and Challenge-Reply Rules You Must Memorize

The authentication section is the one field you can't look up after isolation, because it's gone if you're captured. Memorize the challenge and reply, and carry the card in a place capture won't easily find. Standard practice is to carry the plan inside a marked carrier such as a survival-kit pouch. Confirm the exact carrier and marking with your unit. If you're captured, the recovery force still needs you to respond correctly.

Memorization is the weak point of the whole system. Almost every member carries the card and few test their recall. So run a practical test before departure: write the card, put it away, and recite the challenge and reply. If you stumble, rewrite the mnemonic.

Treat challenge and reply as a matched pair. A correct challenge with the wrong reply will not authenticate you, and an incorrect challenge may mark the caller as hostile. Keep the pair together on the card and memorize them as a unit.

The phrase can fail you in a real extraction. A recovery crew that receives your reply but also sees a weapon in your hands may still treat you as a threat. Add a note to your plan on how you'll present yourself, hands visible, weapon down, at the first contact.

Standoff Signaling: Panels, Flares, and Radios in the Plan

Build the signaling plan as a sequence with times, not as a list of gear. Decide what you'll show at each contact point, in what order, and at what hours. Then write a code phrase for the radio if one is issued. A plan that assumes radio contact will be silent the moment the radio dies.

Visual signals matter because they need no power. A panel spread on the ground, a mirror flash in daylight, or a flare at night all reach an observer who can't hear you. Cronin and colleagues, writing in Wilderness & Environmental Medicine in 2016, documented that mirrors and improvised signals have long been used because they work at distance. Flares need conservation, so reserve them for a confirmed aircraft or team with an established pattern, not a first sighting.

Radio behavior belongs in the plan. Time windows for transmissions, the challenge and reply for voice, and expected frequency are standard entries. If the radio plan fails, fall back to visual signals and a planned movement toward a contact point.

Signal timing protects you as much as it finds you. A flare fired at a distant noise gives away your position. Mark the hours when you'll signal and hold to them.

Failure Cases That Get Isolated Members Caught

Plans fail in predictable ways, and every one is worth a rehearsal. These are the cases to test against your card before you deploy.

Stale authentication. Your reply is out of date and the recovery crew treats you as a trap. Test the pair in field exercises. Silent radio. The radio dies and you never designated a visual fallback. Rehearse the panel and mirror. No holding time. You leave a contact point on day one and the recovery force arrives on day three. Write the holding period on the card. Wrong contact point. The route names a junction that a new road has replaced. Use current maps and a route drawn before departure.

Failure in evasion is rarely a single dramatic mistake. It's usually a chain: a lost radio, a missing fallback, and a decision to move when the plan said wait. The plan is only as good as your ability to execute it under stress, which is why rehearsal matters as much as writing.

A recoverable position can become unrecoverable in a single judgement call. Leaving a contact point early because the area felt exposed, without telling the plan, strands the recovery force at the wrong location. Write the decision rule before departure.

What This Looks Like for a Downed Aircrew

The classic EPA case is a downed aircrew member in hostile territory. The plan is done before the flight, and the mission brief confirms the route, the challenge and reply, and the contact points. Once isolated, the crew member opens the plan, moves to the first point, and radioed or visual contact begins within the recorded windows. The Air Force Handbook 10-644's planning section is the reference for the format.

The sequence shifts with the platform. A pilot who ejects from a fighter aircraft has a survival kit built into the seat and a short window to evade before pursuit. A transport crew may go down as a group, which changes signaling: multiple people, one plan, and a challenge and reply that the whole team can use. The plan still records the same five elements.

Signal windows get tight when the recovery force is an armed aircraft that can't land. In that case, the aircraft's pass schedule sets the clock. Flight manuals and unit SOPs cover exact formats, and the plan must match. The brief between crew and rescue is the real coordination point.

Write your own plan line by line, test it in a field exercise, and don't carry a card you haven't rehearsed. Your memory, your map, and your signal kit are the plan.

Regional and Service Differences You'll Notice in Real Plans

Formats vary by service and region, and the difference can trip you up. The US Air Force's planning checklist in Handbook 10-644, the Army's survival field manual, and Navy and Marine Corps programs each set a slightly different card and carrier. The items overlap: authentication, route, contact points, signaling, and capture criteria appear across them. Confirm the exact format and carrier with your unit's conducting authority, not with a generic manual.

Region shapes the plan more than the format does. A desert plan leans on named terrain features and long visual signals. A maritime plan names sea-state and daylight windows. A mountain plan lives or dies on passes and valley routes. Contact points must match the terrain the recovery force can actually reach.

International partners may use a different authentication vocabulary, and the challenge and reply for a coalition recovery may differ from your national one. Ask what applies when a coalition aircraft or ground team is the recovery force.

Whatever the service, the plan remains a personal document. It records your decisions, not a generic template. That personal detail is why recovery forces can use it.

Cases Where the Written Plan Deliberately Stays Blank

Sometimes the plan is the thing that must remain unrecorded. If exploitation is a live risk, the command may authorize leaving capture and information-disclosure fields blank, or restrict what's written to authentication and contact points. Follow the governing instruction, not the temptation to fill every line. A complete plan that exposes a team, a route, or an information-dump limit is worse than a partial one.

Who can be told matters. An EPA is a personal planning document, and its contents are protected under the same handling rules as other operations material, per your unit's security instruction. Sharing route and authentication data beyond the recovery force creates a leak path.

Some fields change without notice, like authentication countersigns and radio codes. The plan should include a review step before each mission, and the review is where stale entries get caught. If you can't review, treat the card as a draft.

Never carry a blank card as a good-luck token. A blank plan gives recovery forces nothing to authenticate and nothing to find. The card is a tool that must be filled and rehearsed.

FAQ

What does EPA actually stand for here?

In survival planning, EPA stands for Evasion Plan of Action. In environmental regulation it stands for Environmental Protection Agency, and those two uses have nothing to do with each other. This article covers the survival-planning version.

Is an Evasion Plan of Action legally required?

It's required by service and command instruction, not by civilian statute, and the exact obligation comes from your unit's governing publication. No civilian court imposes it. If you work in a program that requires one, the requirement lives in the training and readiness instruction.

How fast must a plan be put into action after isolation?

The plan should move into execution within hours of isolation, not days. Recovery windows can close quickly because evasion gets harder as pursuit starts and the terrain becomes known to the search. That applies once you've made deliberate contact with recovery forces.

How many days should a holding period cover?

Holding periods should be set long enough to cover several days of search, and the exact number should be agreed with the recovery force before departure. Set a defensible holding period rather than a short one. If the recovery element expects to reach the area within a set cycle, your holding period must extend past it.

Can I memorize the plan instead of carrying it?

Carrying the card is the standard practice, and memorization alone fails under stress because recall degrades. The card is written, carried, and memorized. If the card is lost or captured, memorized authentication is your fallback.

Does the plan cover capture and detention?

The plan's capture criteria set limits and information-disclosure rules, and they tie into the resistance training that accompanies evasion. They don't replace the code of conduct or your command's instruction on release of information.

There's an information-handling failure case worth stating plainly: a member who writes a complete route and authentication on an unsecured slip and loses it at a waypoint has handed a map to the search effort. Write with a cheap pen, laminate at the unit's discretion, and keep the card where a quick capture won't reach it.

What should I do if I lose the plan?

If the card is lost, keep the memorized challenge and reply and report the loss through your unit's security channel as soon as you can. A lost authentication card is a potential compromise and may trigger a change to the countersign. Don't improvise a substitute without authorization, and if a recovery contact asks for authentication you can't recall, say so rather than guess.

That completes the answer the keyword asks for. Your plan is only as good as the five items on it and the rehearsal behind them, and recovery forces can use the card only if it reaches the field filled and tested.