Position Reporting
Edit on GitHubReporting a position to a rescue team: the format question, the read-back rule, and what to say with the beacon's coordinates in hand.
Position Reporting
Giving a position is easy; giving a position a rescue team can act on is a skill. The difference is format, confirmation, and context.
The format question
Before you state a single number, ask (or state) the format:
| Format | Example | Used by |
|---|---|---|
| Decimal degrees | 45.8325 N, 6.8650 E | This beacon’s payload |
| DDM | 45 49.950 N, 6 51.900 E | Many topo maps, some teams |
| UTM | 32T 323450 E 5077600 N | Many rescue teams, military |
If the team asks for UTM and you have decimal degrees, convert (see Coordinate Conversion) or say clearly: “I have decimal degrees, can you accept that?” Most teams can; the failure mode is silently assuming a format.
The read-back rule
After giving the position, the professional practice is:
- The receiver reads the numbers back.
- You confirm or correct.
- Only then is the position logged.
If the team does not read back, ask them to. A transcribed digit error has started more searches than any other cause.
What to add
| Element | Example |
|---|---|
| Landmark | “On the ridge above the Refugio” |
| Altitude | “At 2400 meters” |
| Movement | “Walking east along the trail” |
| Time | “Position as of 14:30” |
The beacon’s contribution
The beacon payload carries the position continuously, so even if your voice call fails, the team has the numbers. Check before the trip that the payload coordinates are current (or GPS is enabled): a stale coordinate is worse than none, because it sends the team to the wrong place.
Related pages
- Coordinate Conversion for the math
- GPS Coordinate Systems for the formats
- Incident Command for how the report is used