Float Plan Template: What to Include and Update

A float plan template isn’t busywork. It’s the fastest way to turn “we think they went somewhere around…” into a targeted Search and Rescue (SAR) response with the right assets, in the right water, at the right time. The trick is writing it for the person who will make the call—and for the watchstander who has to act on it—using identifiers, waypoints, and a hard overdue trigger.

Photo by Volodymyr Hryshchenko on Unsplash

What a Float Plan Is (and Isn’t): SAR-Ready, Not a Paperwork Drill

Float plan vs. passage plan vs. “filing” with authorities

A boat float plan is a shore-held snapshot: who’s aboard, what you’re on, where you intend to go, when you’ll check in, and exactly when to raise the alarm. It’s designed so a non-boater can read it to the Coast Guard without translating “we’ll poke around the bay.” A passage plan (or yacht passage plan template) is your onboard navigation and seamanship document—courses, tides, weather routing, alternates, fuel planning, and “what if it goes sideways.”

In most recreational cases in the U.S., you do not “file” a float plan with USCG like an IFR flight plan. The U.S. Coast Guard Auxiliary (USCGAUX) guidance is straightforward: leave it with a trusted shore contact and include a precise overdue instruction (for example, “If no check-in by 2000, call USCG at 2100”). That single line prevents hours of dithering and “maybe they’re just running late.”

Why SAR outcomes improve with better identifiers and time triggers

SAR hates ambiguity. If your plan says “headed toward the islands,” the search area balloons with every minute, and the first asset gets launched into a guess. If instead you provide HIN (12 characters on U.S.-built boats), MMSI (9 digits), and EPIRB/PLB HEX ID/UIN, responders can cross-check databases, radio calls, and beacon hits fast.

Your float plan form should read like a “vessel intelligence card,” not a diary. Add hull color, stripe color, rig type, and tender details (like “10 ft inflatable, white tubes, outboard on bracket”). Those descriptions get broadcast to other boats and aircraft, and they’re more useful than your boat’s nickname.

What “overdue” means operationally and why your trigger matters

“Overdue” is not “a few hours late.” Operationally, overdue means your shore contact has hit a pre-agreed clock time and starts a scripted escalation. USCGAUX-style timing works because it forces action: missed check-in at 2000, call authorities at 2100, not “sometime tonight.”

A good float plan template also acknowledges reality: cell coverage drops behind headlands, marinas close offices, and people forget. You can reduce false alarms by building check-in windows (earliest/most likely/latest), but you still need a hard trigger. If you’re routinely “a bit late,” fix the plan, not the discipline.

Captain’s tip: If your overdue trigger feels “too soon,” your check-in schedule is probably too vague. Tighten the check-ins, then keep the trigger firm.

Photo by Compagnons on Unsplash

Float Plan Form: Exact Fields That Matter Most to Rescuers

Vessel identifiers and physical description (make it unmissable)

Start with what SAR can confirm quickly. Vessel name and registration/documentation number are basic, but don’t stop there: add the HIN (12 characters), the MMSI (9 digits) for DSC/AIS, and a call sign if you have one via an FCC ship station license (common for some international use under 47 CFR rules). If you carry an EPIRB or PLB, write the HEX ID/UIN exactly as labeled, character-for-character.

Physical description is not fluff. Record LOA in feet/meters, hull and deck colors, stripe colors, and rig type (sloop/cutter/ketch; powerboat cabin/center console). Add distinctive marks: solar panels on the stern arch, a red dodger, a radar dome, or a bimini that looks like a stretched bedsheet (we’ve all seen it).

Crew manifest + medical notes that change the response

SAR planning changes with people details. List each person’s full legal name, age, role (skipper, crew, passenger), and phone number. Include medical conditions (diabetes, seizures), allergies, and critical meds; one EpiPen aboard versus none is meaningful.

Also list PFD sizing and type aboard: “4 × USCG Type I (adult), 2 × youth Type III,” for example. USCG carriage rules are clear: one USCG-approved wearable PFD per person, and a throwable device for boats ≥16 ft (with common exceptions like canoes/kayaks). That’s compliance, but it’s also survivability intelligence.

Route, waypoints, and ETA windows (written for a non-boater)

Write route blocks so a shore contact can speak them aloud. Use named points plus coordinates, and keep the coordinate format consistent (either decimal degrees or degrees + decimal minutes). Include 2–6 waypoints for most coastal trips, plus leg distances in nautical miles (NM) and a conservative speed in knots.

Don’t write one single ETA unless you enjoy unnecessary panic. Use a window: earliest/most likely/latest arrival. And include a “hard turnaround time,” like “If not past WP2 by 1500, divert to Harbor X,” so the search area doesn’t become an open-ended smear.

If you want clean leg distances quickly, use a tool to calculate the distance between ports to total NM between waypoints and sanity-check your route. It’s also handy for estimating motoring fuel needs based on voyage distance if the breeze quits at the worst possible time (which it will, eventually).

Safety gear and compliance fields worth recording

A float plan isn’t a gear list for bragging rights, but some items matter operationally. Record VHF type (handheld/fixed), any AIS transponder, and beacon details. Then list safety gear with dates and capacities: flares/VDS expiry, fire extinguishers count/type/location (ABYC H-25 and related fire-fighting guidance are worth aligning with), liferaft capacity and last service (ISO 9650 for many offshore rafts).

Add engine and fuel realism. For an auxiliary sailboat, record fuel capacity and typical burn—0.4–1.0 gal/hr is a common range, but your logbook should provide your real number. That lets you validate whether “we’ll just motor home” is credible or a pleasant fiction.

Photo by Scott Blake on Unsplash

Route Planning in a Float Plan: NM, Knots, Waypoints, and ETAs

How to express distance and time: NM + knots + contingencies

Keep the math simple and conservative, because your shore contact will repeat it under stress. The core formula belongs right in your planning notes: Time (hours) = Distance (NM) ÷ Speed (knots). If your trip is 18 NM and you plan 6 knots, that’s 3 hours—before you add traffic, sail changes, current, and the five-minute “quick fix” that becomes 40 minutes.

Use planned speed, not best-day speed. A sailboat that can hit 7.0 knots on a reach might average 4.5–5.5 knots once you include tacks, reefing, and current. For powerboats, plan with a realistic cruise setting, not wide open throttle, and account for sea state that can drop speed by 20–40% in steep chop.

If you’re plotting legs, plan your route using a sea distance calculator is a practical way to get NM totals and check your assumptions. Don’t let “it’s not far” be your planning standard; I’ve heard that phrase moments before a squall line arrives.

Waypoint formatting (lat/long) and leg-based ETAs

Waypoints should be precise enough to be useful, but not so “fancy” they become unreadable. Stick to one format: either DD° MM.mmm’ (degrees and decimal minutes) or DD.ddddd° (decimal degrees). Give each waypoint a short name: “WP1 OUTER BUOY,” “WP2 CAPE POINT,” and include a plain-English descriptor a non-boater can say without shame.

Leg-based ETAs reduce confusion. Instead of “arrive around sunset,” provide “Depart 1200, WP1 1300–1330, WP2 1500–1600, arrive 1700–1830.” That windowing prevents false alarms but still supports a firm overdue trigger. It also helps SAR because the search radius grows with time, and last-known position is everything.

Alternate ports, bolt-holes, and a “no later than” turn time

Alternates are where experience shows. List 1–3 bolt-holes that make sense with the wind and sea state, not just the ones with good restaurants. For a coastal hop, that might be “Harbor A (all-weather), Harbor B (good in N–E winds), Marina C (fuel/repairs).”

Include a “no later than” turnaround time. Example: “If not past WP2 by 1500, return to Departure Harbor; if past WP2 but weather deteriorates, divert to Harbor B.” This prevents the worst float plan failure mode: an open-ended outing with no boundary conditions, where overdue becomes a debate instead of a decision.

Photo by Kelly Sikkema on Unsplash

Who to Leave a Float Plan With: Shore Contact Selection + Playbook

Selecting a shore contact who will actually act

Pick someone who is responsible, reachable, and comfortable making phone calls. Boating expertise is optional; reliability isn’t. The best shore contacts I’ve used are the kind of people who show up on time and don’t freeze when the plan says “call USCG.”

Use two contacts: a primary and a backup, with a clear handoff. If your primary is on a flight or in surgery, your backup needs the same packet and the same authority to act. Put both phone numbers on the float plan itself, so responders can coordinate.

What to send them (and what not to rely on)

Send the plan as a PDF (and ideally printed), plus a small photo set: port/starboard profile, transom, rig, and dinghy/tender. Add any tracking links you use (AIS web view, sat messenger map), and include marina and harbormaster phone numbers along your route.

Do not rely on “we told the dockmaster,” a social media post, or a vague group chat. Those are not a trip plan for boating; they’re a rumor. People go off shift, phones die, and nobody wants the responsibility when the story is fuzzy.

The shore-contact escalation script (staged actions)

Give your shore contact a simple staged checklist with times. USCGAUX-style wording is gold: “If no check-in by 2000, call USCG at 2100.” The hour in between is for attempts and verification, not procrastination.

Stage it like this: (1) call/text skipper and each crew number; (2) check tracking links (AIS/sat messenger) and last update time; (3) call marinas or likely bolt-holes; (4) call USCG and read the plan verbatim, including vessel name, HIN, MMSI, HEX ID/UIN, persons aboard, and last known waypoint/ETA. You’re not asking permission to worry—you’re executing a pre-briefed procedure.

Photo by Felicia Buitenwerf on Unsplash

When to Update a Float Plan: Check-Ins, Overdue Triggers, and Versioning

Check-in cadence by trip type (day sail vs. multi-day)

A float plan that never gets updated becomes historical fiction. For day trips, plan 2–4 check-ins: departure, mid-route (or at a decision waypoint), and arrival. If the area has known dead zones, shift check-ins to points where you expect coverage, like outside headlands rather than behind them.

For multi-day trips, schedule at least one daily check-in at a fixed time, plus “event-based” check-ins at major waypoints. It’s boring, and that’s the point; boring is predictable, and predictable is rescuable. If you’re using a tracker, still do voice/text check-ins—electronics fail on the days you least want them to.

What changes require an immediate update (route/crew/gear)

Update means a timestamped revision, sent to the shore contact who will act. If your destination changes, send a v2 with new waypoints and ETAs. If someone new joins or leaves, update the crew manifest and medical notes; “we’ve got one extra friend” is not a detail to improvise during an overdue report.

Update if your comms or safety gear status changes in a meaningful way: VHF swapped, MMSI reprogrammed, EPIRB moved, liferaft serviced, or a key battery issue develops. Beacon registrations (NOAA SARSAT in the U.S.) are free and easy to keep current, but only if you treat them like a living record.

Overdue logic: reducing false alarms without delaying SAR

False alarms waste resources and goodwill, but delayed alerts cost lives. A sensible approach is a staged plan with a hard call time: if you miss a check-in, the shore contact begins attempts immediately, then calls authorities 1–3 hours later depending on local conditions. But you must specify the exact clock time in the plan, every trip.

Don’t set overdue triggers based on optimism. Set them based on worst-case plausible delay, communications gaps, and the fact that SAR response time is not instant. If your route crosses heavy traffic or cold water, err earlier; the sea does not reward your preference for avoiding embarrassment.

Versioning that actually works in practice

Use simple version control: v1 pre-departure, v2 after route change, v3 after crew change, each with “last updated” date/time and a distribution list. That prevents the classic mess where the backup contact has last week’s plan and confidently reports the wrong destination.

If you’re using online tools, keep them simple and redundant. A shared folder with the current PDF, photos, and tracker links works well—until someone’s phone won’t open it offshore. Keep a printed copy onboard too, because sometimes the emergency is not “lost boat,” but “we need to call for help and can’t remember our own beacon ID.”

Photo by yassine ouali on Unsplash

Worked Float Plan Examples (3): Day Sail, Coastal Hop, Overnight

The examples below map directly to a float plan template and show the level of detail that helps SAR without turning your pre-departure into an accounting exercise. Replace placeholders with your real HIN (12 chars), MMSI (9 digits), and HEX ID/UIN.

Example 1: 2–4 hour day sail with local check-ins

Vessel: “S/V LEE SHORE” (yes, I’ve seen worse names), 32 ft sloop, white hull with blue stripe, 10 ft white inflatable on davits. IDs: HIN ABC12345D626, MMSI 367123456, AIS Class B (2 W) MMSI 367123456, PLB HEX ID A1B2C3D4E5F6789. Persons: 3 aboard; one has a peanut allergy; EpiPen in nav station.

Route: Depart City Marina 1300, sail inside the bay to WP1 (Bay Bridge) then WP2 (Outer Buoy) then return. Legs: City Marina→WP1 3.5 NM; WP1→WP2 4.0 NM; WP2→City Marina 5.0 NM. Planned speed 5.0 kt average; time = 12.5 NM ÷ 5.0 kt = 2.5 hours underway, plus 0.5 hour slack for traffic and sail handling.

Check-ins: “Departed” at 1300; “At WP2” 1430–1500; “Back at dock” 1630–1730. Overdue: “If no check-in by 1730, call skipper/crew; if no contact, call USCG at 1830.” Fuel: 15 gal aboard; typical burn 0.6 gal/hr; motoring contingency 2 hours = 1.2 gal.

Example 2: Coastal hop between ports with alternates

Vessel: 38 ft cutter, blue hull, tan deck, radar dome on mast, orange liferaft canister on stern rail. IDs: HIN XYZ98765E626, MMSI 338987654, EPIRB HEX ID 0F1E2D3C4B5A697. Crew: 4 aboard; one asthmatic (inhaler in grab bag); all adults; PFDs 6 wearable, 1 throwable (boat >16 ft).

Route: Port A to Port B, staying 2–5 NM off. Waypoints: WP1 Sea Buoy, WP2 Cape Point, WP3 Harbor Entrance. Distances: Port A→WP1 6 NM; WP1→WP2 14 NM; WP2→WP3 10 NM; total 30 NM. Planned speed 6.0 kt conservative; time = 30 ÷ 6 = 5.0 hours underway, plus 1.0 hour margin.

Alternates/bolt-holes: Harbor X (good in southerlies), Harbor Y (fuel and repairs). Decision point: “If not past WP2 by 1500, divert Harbor X.” Check-ins: Depart 0900; WP2 report 1300–1400; arrival Port B 1500–1700. Overdue: “No arrival check-in by 1700 → call USCG at 1900.” Use Breezada’s sea distance calculator beforehand to verify NM totals and keep your ETAs grounded.

Example 3: Overnight passage with waypoint-based ETAs

Vessel: 45 ft sloop, gray hull with black stripe, tender 9 ft RIB towed (yes, we’ll argue about towing offshore later). IDs: HIN QRS24680F626, MMSI 366246802, AIS Class B (2 W), EPIRB HEX ID 1A2B3C4D5E6F7A8. Crew: 5 aboard; one on daily medication (stored in labeled dry bag); passports onboard.

Route: Island A to Island B overnight. Waypoints: WP1 Departure Gate, WP2 Midpoint, WP3 Arrival Gate. Legs: WP1→WP2 42 NM; WP2→WP3 38 NM; total 80 NM. Planned speed 5.5 kt conservative; time = 80 ÷ 5.5 = 14.5 hours. ETA windows: Depart 1600; WP2 0000–0200; arrive 0600–0900 depending on current and sail plan.

Check-ins: “Departed” 1600; “WP2” by sat message at 0200 latest; “Arrived” 0900 latest. Overdue trigger: “If no arrival by 0900, attempt contact; call USCG at 1100 with route and beacon IDs.” Fuel: 40 gal; burn 0.8 gal/hr; motoring contingency 10 hours = 8 gal, leaving reserve.

Communications & Distress Data: MMSI, DSC, EPIRB/PLB, AIS

VHF voice vs. DSC: what to record and why it’s SAR-useful

In the U.S., voice distress and calling uses VHF Channel 16 (156.800 MHz). If you can only remember one thing under stress, it’s that. But for a modern float plan, DSC details matter because a DSC distress alert includes your MMSI and position (if properly interfaced).

Record whether your VHF is fixed-mount or handheld, whether it’s DSC-capable, and whether the MMSI is programmed. MMSIs are 9 digits, and getting one is usually free or low-cost through approved issuers for domestic use (BoatUS/USPS), while some international operations require FCC licensing under 47 CFR. If your radio has never had its MMSI entered, that red distress button is mostly theater.

Also note your monitoring plan: “VHF on, Ch 16 watch, DSC enabled.” It sounds basic, but responders will ask, and it shapes how they try to reach you.

Beacon identifiers and registration hygiene (NOAA SARSAT)

EPIRBs and PLBs typically transmit on 406 MHz and include a 121.5 MHz homing signal used by nearby assets. In the U.S., registration through NOAA SARSAT is free, and it’s not optional in any practical sense—unregistered beacons create delays while SAR tries to figure out who you are.

Put the HEX ID/UIN in the float plan exactly as printed, and confirm your registration contacts match your current shore contacts. If you changed phone numbers last year and never updated NOAA, you’ve built a delay into your own rescue. Record service dates too: EPIRB battery life is often around 5 years, and many HRUs are commonly replaced around 2 years (verify the label on your unit).

Tracking and redundancy: AIS, sat messengers, and power

AIS can be hugely helpful in trafficked waters. Record AIS class and MMSI: Class B typically transmits at ~2 W, Class A at ~12.5 W. If your shore contact knows you transmit AIS, they can check recent positions via your preferred AIS service or app, and responders can query systems on their end.

Sat messengers (Garmin inReach / Zoleo category) add another layer, but only if they’re charged and the account is active. Record the device type and the tracking link, plus how often it updates (every 10 minutes, 30 minutes, etc.). If your plan relies on a tracker that pings every 2 hours, don’t pretend it’s real-time.

Power is the quiet failure point. Comms gear depends on batteries and charging systems; ABYC E-11 thinking applies even if you’re not rewiring the boat. Note your charging sources (alternator, solar, generator) and keep at least one independent option for the handheld VHF, because “silent boat” is a common prelude to bad outcomes.

Common Float Plan Mistakes + A Practical Checklist and Cost Options

Mistakes that expand the search area and waste time

The highest-impact mistakes are boring: vague destination, no waypoints, no crew list, missing overdue trigger, and outdated phone numbers. Next is missing technical identifiers that actually let SAR confirm you: HIN (12 chars), MMSI (9 digits), and beacon HEX ID/UIN. If your plan says “blue sailboat,” congratulations—you’ve described half the anchorage.

Another common error is the “infinite outing.” No turnaround time, no alternates, and no decision points means your shore contact can’t say where you might be when things drift. If you’re using Breezada’s sea distance calculator to plan your route, copy the leg NM numbers into the plan; don’t leave them stuck on your laptop at home.

SAR-useful extras: photos, tender details, and service dates

Photos are underused and extremely effective. Include 4–6 images: profile shots, transom, rig, and the dinghy (length in ft/m, color, where stored). A tender adrift becomes a separate incident fast, and SAR wants to know if yours is towed, on davits, or on deck.

Service dates matter because they change confidence. Record EPIRB battery expiry (5 years common), HRU replacement (2 years common), liferaft service date, and VDS/flares expiry. That’s not bureaucracy; it’s evidence that the gear you’re counting on is more than decoration.

Low-cost ways to store and share your plan (paper + digital)

Use redundancy, because phones fail, printers run out of ink, and shared links get buried. A printed plan at home plus a PDF to your shore contact covers most bases. If you use a cloud doc, lock down editing so nobody “cleans it up” mid-trip.

Here are practical storage/sharing options and how they fail in real life:

And if you’re budgeting upgrades that materially improve the “comms and locate” side of your plan, typical ranges look like this:

Float plan checklist (print this): Vessel IDs (HIN/MMSI/HEX ID), hull/rig/tender description, crew list + medical notes, route waypoints + leg NM/ETAs, alternates + turnaround time, comms block (VHF/DSC/AIS/sat), safety gear + service dates, check-ins + exact overdue-call time, version/date sent to shore contacts.

Frequently Asked Questions

Where do I find my EPIRB/PLB HEX ID (UIN), and how should it be written in a float plan so SAR can use it without confusion?

The HEX ID/UIN is printed on the beacon label (and often on the registration paperwork), typically as a string of hexadecimal characters. Copy it exactly as shown—same characters, same grouping if present—and label it clearly as “EPIRB HEX ID” or “PLB HEX ID.” Don’t rewrite it from memory, and don’t assume the shore contact can “find it online” during an overdue call.

If my VHF has DSC, what exact identifiers must be in the float plan (9-digit MMSI, radio type, programmed status), and what channel/frequency does the DSC distress alert use?

Record the 9-digit MMSI, whether the radio is fixed-mount or handheld, and whether the MMSI is programmed and active (many radios show this in the menu). Include that you monitor Ch 16 (156.800 MHz) for voice. DSC distress alerts transmit on VHF Channel 70 (156.525 MHz), so responders will care whether your DSC function is actually configured.

How should I format waypoints (lat/long) and leg ETAs so a non-boater shore contact can read them accurately to the Coast Guard during an overdue vessel report?

Use a consistent coordinate format—either decimal degrees or degrees and decimal minutes—and stick with it for every waypoint. Name each waypoint simply (WP1, WP2) plus a plain-English label, and provide leg distances in NM and ETAs as windows (earliest/most likely/latest). The goal is a script your shore contact can read verbatim without translating “somewhere near the point.”

For an auxiliary sailboat, how do I compute and record a realistic motoring contingency using fuel capacity and typical burn (gal/hr) to keep ETA windows credible?

Record two numbers from your own logbook: typical cruising RPM burn (often 0.4–1.0 gal/hr for many auxiliaries) and usable fuel aboard in gallons. Motoring hours available ≈ fuel aboard ÷ burn rate; then estimate motoring range ≈ hours × your typical motoring speed in knots. Write the contingency plainly in the plan (e.g., “Fuel 20 gal; burn 0.6 gal/hr; 10 hr contingency = 6 gal; reserve 10 gal”).

If my boat transmits AIS, what details belong in the float plan (AIS Class A vs B, MMSI, transmit power), and how does that affect what a shore contact should check first?

Record AIS class, MMSI, and (optionally) the typical transmit power: Class B ~2 W and Class A ~12.5 W. Include any AIS tracking link you prefer and the vessel name as it appears on AIS targets. If you miss a check-in, AIS is often the fastest first check in coastal traffic—if the transponder is on and the antenna/power are healthy—before moving to marina calls and then the overdue report.

---

A good float plan template is a shore-held, SAR-optimized document: clear vessel and crew identifiers, leg-based route and ETA windows, comms and beacon numbers, and a timestamped overdue escalation plan. Keep it as a living document, send it to a reliable shore contact (and a backup), and update it immediately when route, crew, or key gear changes. And when you’re estimating leg distances and time, use Breezada’s sea distance calculator so your ETAs are based on NM and knots—not hope.