Position reporting forms the backbone of aviation safety and communication. In this comprehensive guide, you’ll learn the exact formats and procedures for reporting your aircraft’s position during every flight phase. From pre-flight to landing, proper position reporting ensures controllers track your movement, other pilots maintain situational awareness, and you navigate safely through the airspace system.
The Fundamentals of Aviation Position Reporting
Position reporting in aviation serves critical safety and operational functions. Before examining specific formats for each flight phase, it’s essential to understand the fundamental elements that make up a standard position report and why each component matters.
| Photo | Popular Portable Walkie Talkies | Price |
|---|---|---|
| Multifunctional Smart Wireless Ski Goggles with Walkie-Talkie, Replaceable Anti-Fog Lens, Music & Call, Real-Time AMOLED Display, Compatible with Most Helmets (G03 Blue, Multi-Button Remote) | Check Price On Amazon |
| SINORISE Super Mini Walkie Talkies, Portable Two-Way Radios for Restaurants, Outdoor Sports, Retail Stores, Hospital & Travel – 3 Pack | Check Price On Amazon |
| KOSPET Tank M4C Outdoor Smart Watch with GPS, 1.96" AMOLED Display, Built-in LED Flashlight & Walkie-Talkie, Long Battery Life, 50m Waterproof, Bluetooth Calls, 24/7 Heart Rate/Sleep Monitor | Check Price On Amazon |
| Retevis RT15 Walkie Talkies, Portable FRS Two Way Radios Rechargeable, Durable, Compact, VOX, Key Lock, Mini Walkie Talkies for Adults and Kids, School Family Outdoor Travel Camping Hiking (3 Pack) | Check Price On Amazon |
| Rechargeable Walkie Talkies Toys for Kids: DIY Astronaut Walkie Talkies for Boys Christmas Birthday Gifts for 3 4 5 6 7 8 9 10 Boy Walkie Talkie Outdoor Hiking Toy 2 Way Radio Camping Outdoor Game | Check Price On Amazon |
A position report is a standardized communication from an aircraft to air traffic control (ATC) or other aircraft that provides specific information about the aircraft’s location, altitude, timing, and intentions. According to the FAA Pilot/Controller Glossary, a position report contains “information relating to the position of the aircraft in reference to navigational aids, fixes, or waypoints.”
Position reports serve several key purposes:
- Establish and maintain situational awareness for controllers and pilots
- Enable traffic separation in both radar and non-radar environments
- Track flight progress along planned routes
- Provide critical safety information during all phases of flight
- Facilitate coordination between different control facilities
The requirements for position reporting vary significantly between IFR (Instrument Flight Rules) and VFR (Visual Flight Rules) operations. IFR flights have more stringent, regulatory requirements, while VFR reporting often follows recommended best practices unless specific circumstances dictate otherwise.
Essential Elements of a Complete Position Report
Every complete position report contains specific elements in a standardized sequence. Understanding these components ensures nothing critical is omitted during your communications.
A standard position report includes these six elements in sequence:
- Identification: Aircraft call sign or tail number
- Position: Current location (fix, intersection, navaid, or visual reference)
- Time: Time over the reported position (UTC/Zulu)
- Altitude: Current altitude or flight level
- Next Fix: Next reporting point or destination
- ETA: Estimated time of arrival at next reporting point
- Following Fix: Point after the next reporting point (when required)
For example, a complete IFR position report might sound like: “Boston Center, Cessna Three Four Five Six November, over Augusta VOR at one-eight-four-five Zulu, maintaining six thousand, estimating Portland VOR at one-nine-zero-zero, Kennebunk next.”
In radar environments, controllers often permit abbreviated reports, but in non-radar environments or during radar outages, all elements become mandatory for IFR flights per AIM 5-3-2.
Position Reporting Phraseology and Techniques
Proper aviation phraseology ensures your position reports are clearly understood by ATC and other pilots. These standardized communication techniques minimize confusion and enhance safety.
Radio discipline is essential for effective position reporting and follows these key principles:
- Numbers pronunciation: “Niner” instead of “nine,” “tree” instead of “three”
- Altitude statements: “Six thousand five hundred” not “sixty-five hundred”
- Directional references: “Heading zero-nine-zero” not “heading ninety”
- Communication pace: Speak at a moderate, clear pace
- Brevity: Include all required elements without unnecessary words
For example, instead of saying “I’m approximately twenty miles south of the airport at about three thousand five hundred feet,” say “Twenty miles south, three thousand five hundred.”
Common phraseology errors include using contractions (“I’m,” “we’re”), non-standard terms (“taking off” instead of “departing”), and inconsistent position descriptions (“near” versus specific distances).
Pre-Flight Position Reporting: Ground Operations
Position reporting begins before you leave the ground. Understanding proper ground movement reporting sets the foundation for effective communications throughout your flight.
Your first position report typically occurs when contacting Ground Control for taxi instructions. This initial contact establishes your position on the airfield and intentions:
“Burlington Ground, Cessna Three Four Five Six November, general aviation parking, with information Delta, request taxi for VFR departure to the north.”
After receiving taxi instructions, your readback serves as confirmation of your intended movement path, essentially a forward-looking position report:
“Taxi via Alpha to runway one-five, hold short of runway two-zero, Cessna Three Four Five Six November.”
At non-towered airports, position reporting becomes even more critical as it creates a shared mental model for all aircraft in the vicinity. These reports should reference specific airport locations rather than vague positions.
Taxiing and Ground Movement Position Reports
Reporting your position while taxiing is essential for ground collision avoidance and efficient airport operations. Here’s how to properly communicate your position during ground movement.
At towered airports, position reports during taxi focus on:
- Acknowledgment of instructions with readback
- Reporting hold short compliance: “Cessna Three Four Five Six November, holding short runway one-five”
- Reporting runway crossing: “Crossing runway two-zero, Cessna Three Four Five Six November”
- Reporting position when requested: “Ground, Cessna Three Four Five Six November is at Alpha intersection with Charlie”
At non-towered airports, position reports inform other aircraft of your location and intentions:
“Sebastian Traffic, Cessna Three Four Five Six November taxiing from the ramp to runway five via taxiway Alpha, Sebastian.”
When visibility is limited or you’re unfamiliar with the airport, request progressive taxi instructions:
“Burlington Ground, Cessna Three Four Five Six November, request progressive taxi to Runway one-five.”
Departure Phase Position Reporting
Position reporting during departure transitions from ground operations to establishing yourself in the air traffic system. Each type of departure has specific reporting requirements and expectations.
At towered airports, your first airborne position report occurs when Tower hands you off to Departure Control:
“Burlington Departure, Cessna Three Four Five Six November, climbing through one thousand five hundred for three thousand five hundred, heading three-six-zero.”
This initial departure call provides three critical position elements: identification, altitude (both current and assigned), and direction of flight.
At non-towered airports, departure position reports serve to inform other traffic in the area:
“Sebastian Traffic, Cessna Three Four Five Six November departing Runway five, northbound departure, climbing through one thousand two hundred, Sebastian.”
For Special VFR departures, position reports must include your Special VFR status and intentions to exit the airspace:
“Burlington Tower, Cessna Three Four Five Six November, Special VFR, two miles southeast of the airport, one thousand five hundred, clear of Class Delta, switching to advisory frequency.”
IFR Departure Position Reporting Requirements
IFR departures have specific position reporting requirements that ensure ATC maintains continuous awareness of your flight. Here’s what you need to report and when during an IFR departure.
Before takeoff, readback the entire IFR clearance including:
- Clearance limit
- Route of flight
- Initial altitude
- Departure frequency
- Transponder code
Your initial airborne report must include:
- Aircraft identification
- Current altitude
- Climbing to assigned altitude
- Any assigned heading
Example: “New York Departure, Cessna Three Four Five Six November, passing two thousand, climbing to five thousand, heading one-three-zero.”
In non-radar environments, you must report:
- Time of departure
- When reaching assigned altitude
- Passing each compulsory reporting point
If unable to maintain the minimum climb rate or assigned heading, report immediately: “Departure, Cessna Three Four Five Six November, unable to maintain five hundred feet per minute climb due to aircraft performance.”
VFR Departure Position Reporting Best Practices
While VFR departures often have fewer mandatory reporting requirements than IFR flights, effective position reporting enhances safety and efficiency. These best practices ensure you communicate effectively during VFR departures.
When departing the traffic pattern at a towered airport:
“Tower, Cessna Three Four Five Six November, midfield downwind, will depart the pattern to the north.”
When requesting flight following, include your position, altitude, destination, and aircraft type:
“Boston Approach, Cessna Three Four Five Six November, ten miles northeast of Lawrence Municipal at three thousand five hundred, VFR to Portland, request flight following.”
At non-towered airports, make position reports at:
- Before taxiing onto the runway
- When departing the runway
- When departing the traffic pattern
Example: “Manchester Traffic, Cessna Three Four Five Six November, departing Runway six, left crosswind departure, climbing through one thousand eight hundred, Manchester.”
When transitioning through various airspace classes, report:
- Current position relative to the airspace
- Altitude
- Intentions
- Aircraft identification
En-Route Position Reporting Standards
En-route position reporting forms the backbone of air traffic situational awareness during the cruise phase of flight. Requirements vary significantly between IFR and VFR operations, as well as between radar and non-radar environments.
The standard en-route position report format includes:
- Aircraft identification
- Position
- Time
- Altitude
- Type of flight plan (if needed)
- Next reporting point and ETA
- Subsequent reporting point
- Remarks (when necessary)
The requirements differ substantially between IFR and VFR operations:
| Element | IFR Requirement | VFR Practice |
|---|---|---|
| Position reports at fixes | Mandatory in non-radar areas | Optional unless requested |
| Altitude changes | Must report leaving and reaching | Report when on flight following |
| Time estimates | Required at reporting points | Generally not required |
| Equipment issues | Must report immediately | Must report immediately |
With ADS-B technology, aircraft continuously broadcast position information automatically, but voice position reports remain required in certain circumstances, particularly in non-radar environments.
IFR En-Route Position Reporting Requirements
IFR en-route position reporting follows strict regulatory requirements that vary based on your operating environment. Understanding exactly when and what to report is essential for IFR operations.
In non-radar environments, IFR flights must report:
- When passing each compulsory reporting point (identified on charts with a solid triangle ▲)
- When reaching final altitude
- When leaving any assigned altitude
- When an ETA changes by 3 minutes or more
A complete IFR position report in non-radar environments contains:
“Boston Center, Cessna Three Four Five Six November, KBOS at one-eight-four-five, six thousand, estimating KPWM at one-nine-zero-zero, KPSM next.”
In radar environments, you’re typically only required to report:
- When reaching final assigned altitude
- When instructed to report passing a specific fix
- Any unscheduled altitude changes
- Equipment malfunctions affecting navigation or communication
If uncertain about your position, report immediately: “Boston Center, Cessna Three Four Five Six November, position uncertain, last known position was twenty miles east of Manchester VOR at one-nine-five-zero.”
VFR En-Route Position Reporting Best Practices
While VFR flights have fewer mandatory position reporting requirements than IFR operations, effective position reporting enhances safety and improves service from ATC. These best practices will help you communicate effectively during VFR cruise.
When using VFR flight following, report:
- Initial contact with each new controller (provide altitude and destination)
- Altitude changes (before changing altitude)
- Course changes of more than 30 degrees
- Entering or exiting controlled airspace
Example: “Boston Approach, Cessna Three Four Five Six November, two thousand five hundred, request descent to one thousand five hundred.”
When transitioning through different airspace classes:
- Class B: Contact approach control before entering
- Class C: Contact approach control 20 miles out
- Class D: Contact tower 10 miles out
When reporting position using visual references, be specific:
- Use prominent landmarks visible on charts
- Include distance and direction from the reference
- State your altitude
Example: “Cape Approach, Cessna Three Four Five Six November, eight miles northeast of Hyannis Harbor at two thousand five hundred, VFR to Provincetown.”
Position Reporting in Non-Radar Environments
Non-radar environments require more detailed and frequent position reports since air traffic control cannot directly observe your aircraft on radar. These procedures ensure safe separation in areas without radar coverage.
In non-radar environments, position reports must include all these elements:
- Aircraft identification
- Position (fix, intersection, or navaid)
- Time over reported position
- Altitude or flight level
- Type of flight plan (if needed)
- Next reporting point and ETA
- The reporting point after the next reporting point
- Remarks (when necessary)
Per FAA AIM 5-3-2, these reports are mandatory for IFR flights at all compulsory reporting points, which are marked on en-route charts with solid triangles (▲).
Example of a complete non-radar position report:
“Minneapolis Center, Cessna Three Four Five Six November, over Redwood Falls VOR at one-five-two-five, maintaining seven thousand, estimating Mankato VOR at one-five-four-five, Farmington VOR next.”
Controllers use these detailed reports to:
- Track aircraft positions manually
- Calculate separation between aircraft
- Project future positions based on reported times
- Provide traffic advisories
Approach and Arrival Position Reporting
As you transition from en-route to the approach phase, position reporting requirements change to support the increased precision needed near airports. Proper arrival reporting helps controllers sequence traffic and maintains situational awareness for all aircraft.
Your initial approach contact should include:
- Aircraft identification
- Position relative to the airport or approach fix
- Altitude
- Approach request or ATIS information
Example: “Boston Approach, Cessna Three Four Five Six November, twenty miles northeast of the field, four thousand, with information Charlie, request ILS runway four-right approach.”
During the approach phase, report:
- Established on approach segments
- Procedure turn complete (when applicable)
- Final approach fix inbound
- Visual contact with the runway or airport
Reporting requirements differ significantly between towered and non-towered airports. At towered airports, you’ll follow specific controller instructions, while at non-towered fields, you’ll make standardized position reports to inform other traffic.
IFR Approach Position Reporting
IFR approaches have specific position reporting requirements that help controllers sequence traffic and maintain separation. Understanding these requirements ensures smooth coordination during this critical phase of flight.
Key IFR approach position reports include:
- Procedure turn completion: “Boston Approach, Cessna Three Four Five Six November, procedure turn complete, established inbound.”
- Final approach fix: “Cessna Three Four Five Six November, COHAS inbound, maintaining three thousand until COHAS.”
- Outer marker/locator: “Cessna Three Four Five Six November, outer marker inbound.”
- Visual contact: “Cessna Three Four Five Six November, runway in sight.”
- Missed approach: “Cessna Three Four Five Six November, going missed approach.”
Different approach types have specific reporting requirements:
- ILS approaches: Report established on localizer and glide slope
- VOR approaches: Report procedure turn complete and final approach fix inbound
- RNAV approaches: Report established on final approach course and final approach fix inbound
When coordinating between approach control and tower:
“Boston Tower, Cessna Three Four Five Six November, ILS four-right, five miles final.”
If experiencing equipment or approach issues, report immediately:
“Approach, Cessna Three Four Five Six November, localizer fluctuating, request vectors for another approach.”
VFR Arrival and Pattern Entry Reporting
VFR arrivals require clear position reporting to safely integrate with other traffic. Whether arriving at a towered or non-towered airport, standardized position reports help all pilots maintain situational awareness.
When arriving at a towered airport, your initial call should include:
“Boston Tower, Cessna Three Four Five Six November, ten miles northeast at two thousand, landing Boston with information Delta.”
Follow specific tower instructions for pattern entry. Once cleared, report established on the assigned leg:
“Boston Tower, Cessna Three Four Five Six November, established left downwind runway four-right.”
At non-towered airports, make standardized CTAF position reports at:
- 10 miles out: “Manchester Traffic, Cessna Three Four Five Six November, ten miles south, two thousand five hundred, inbound for landing, will report entering downwind runway six, Manchester.”
- Entering downwind: “Manchester Traffic, Cessna Three Four Five Six November, entering left downwind for runway six, Manchester.”
- Turning base: “Manchester Traffic, Cessna Three Four Five Six November, turning left base runway six, Manchester.”
- Turning final: “Manchester Traffic, Cessna Three Four Five Six November, turning final runway six, full stop, Manchester.”
- Clear of runway: “Manchester Traffic, Cessna Three Four Five Six November, clear of runway six, taxiing to parking, Manchester.”
For non-standard pattern entries, clearly communicate your position and intentions:
“Manchester Traffic, Cessna Three Four Five Six November, five miles south, will enter straight-in final for runway six, Manchester.”
Emergency Position Reporting Procedures
During emergencies, effective position reporting becomes even more critical. Emergency position reports follow modified formats designed to quickly communicate your situation while providing essential location information to rescue services.
When declaring an emergency, follow this sequence:
- Use proper distress/urgency call: “MAYDAY, MAYDAY, MAYDAY” or “PAN-PAN, PAN-PAN, PAN-PAN”
- Aircraft identification
- Nature of emergency
- Position (as precisely as possible)
- Altitude
- Intentions
- Fuel remaining (in minutes)
- Souls on board
Example: “MAYDAY, MAYDAY, MAYDAY, Boston Center, Cessna Three Four Five Six November, engine failure, 20 miles northwest of Manchester Airport, passing through five thousand descending, attempting emergency landing in field, 45 minutes fuel remaining, three souls on board.”
If uncertain of your position during an emergency:
- Provide last known position and time
- Report heading since that position
- Request vectors or direction-finding assistance
- Report any visible landmarks
Even with partial communications capability, prioritize transmitting your identification, position, and nature of emergency.
Distress and Urgency Position Reporting
Distress and urgency situations require modified position reporting techniques that prioritize critical information. Understanding the differences between MAYDAY and PAN-PAN protocols ensures effective communication when it matters most.
MAYDAY (Distress) is used when in grave and imminent danger requiring immediate assistance (engine failure, fire, structural failure).
PAN-PAN (Urgency) is used for urgent situations that aren’t immediately life-threatening (partial power loss, minor control issues, fuel concerns).
For MAYDAY situations, the position report priority order is:
- “MAYDAY, MAYDAY, MAYDAY”
- Aircraft identification
- Nature of distress
- Position (coordinates, distance/bearing from a fix, or visual references)
- Altitude and heading
- Intentions
- Critical details (fuel, souls onboard)
Example: “MAYDAY, MAYDAY, MAYDAY, New York Center, Cessna Three Four Five Six November, engine failure, 15 miles east of Stewart airport, seven thousand descending, attempting emergency landing at Stewart, 30 minutes fuel, two souls onboard.”
For PAN-PAN situations, follow similar format but prioritize information relevant to your specific situation:
“PAN-PAN, PAN-PAN, PAN-PAN, Boston Approach, Cessna Three Four Five Six November, partial engine power loss, 10 miles north of Lawrence airport, three thousand, diverting to Lawrence, 90 minutes fuel, three souls onboard.”
Per AIM 6-3-1, repeat your emergency call on 121.5 MHz if no response is received on your initial frequency.
Position Reporting with Communication Difficulties
Communication difficulties can compromise your ability to report position effectively. These techniques help you maintain position awareness for ATC and other aircraft even when facing radio issues.
For partial communications failure (can transmit but not receive):
- State “TRANSMITTING BLIND” before each position report
- Repeat critical information twice
- Report position more frequently than normal
- Include your intentions clearly in each transmission
Example: “Boston Center, Cessna Three Four Five Six November, TRANSMITTING BLIND, over Manchester VOR at one-nine-zero-zero, six thousand, estimating Concord VOR at one-nine-one-five, TRANSMITTING BLIND, Cessna Three Four Five Six November.”
For complete radio failure, use your transponder to indicate your situation:
- Squawk 7600 (radio failure code)
- Maintain VFR conditions if possible
- Land at nearest suitable airport
Light gun signals from the tower can provide guidance during radio failure:
| Signal | Meaning (in flight) |
|---|---|
| Steady Green | Cleared to land |
| Flashing Green | Return for landing |
| Steady Red | Give way to other aircraft |
| Flashing Red | Airport unsafe, do not land |
ADS-B equipped aircraft continue to transmit position data even during communication failures, providing controllers with your location information.
Special Operations Position Reporting
Special flight operations often require modified position reporting techniques. From formation flying to aerial work, these specialized procedures ensure effective communication in non-standard situations.
Formation flights present unique challenges because multiple aircraft operate as a single unit for ATC purposes. The formation leader typically handles all communications while maintaining responsibility for separation within the formation.
When conducting aerial work such as photography, survey, or pipeline patrol:
- Include the nature of the operation in initial contact
- Report operating altitude blocks rather than specific altitudes
- Provide estimated time in the area
- Report specific patterns or routes you’ll follow
Example: “Boston Approach, Cessna Three Four Five Six November, ten miles southwest of Lawrence airport, two thousand five hundred, aerial photography along the Merrimack River for approximately one hour, request advisories.”
For instructional flights with practice approaches or maneuvers:
“Boston Approach, Cessna Three Four Five Six November, fifteen miles northeast of Beverly Airport, three thousand, request practice RNAV runway one-six approach at Beverly, then return to Beverly for landing.”
When operating in special use airspace, position reports should include:
- Entry point and time
- Planned route through the airspace
- Estimated exit point and time
- Operating altitude
Formation and Group Flight Position Reporting
Formation and group flights present unique position reporting challenges. These specialized procedures ensure that controllers and other aircraft understand both your individual aircraft and the overall formation.
For ATC communications, the formation leader:
- Identifies the formation in initial contact: “Boston Approach, Cessna Formation, Three Four Five Six November flight lead”
- Specifies number of aircraft: “Cessna Formation, three aircraft”
- Reports position for the entire formation
- Requests clearances and acknowledges instructions for all aircraft
When a formation element breaks away:
“Boston Approach, Cessna Three Four Five Six November, breaking away from formation, two miles east of Beverly Airport, two thousand five hundred.”
For rejoining formations:
“Boston Approach, Cessna Three Four Five Six November, rejoining Cessna formation, three miles southeast of Beverly Airport, three thousand.”
Military formations typically use specific terminologies:
- “Flight of X” (specific number of aircraft)
- “Standard formation” (within 1 mile laterally and 100 feet vertically)
- “Tactical formation” (within 3 miles laterally and 1000 feet vertically)
Civilian formations generally maintain closer spacing and use more flexible terminology, but should clearly communicate the number of aircraft and overall formation dimensions.
Position Reporting Technology Integration
Modern aviation technologies are changing how aircraft report position. Understanding how ADS-B, CPDLC, and other digital systems integrate with traditional voice position reporting helps pilots navigate this evolving landscape.
ADS-B (Automatic Dependent Surveillance-Broadcast) automatically transmits an aircraft’s position, altitude, speed, and identification to ATC and other nearby aircraft. This technology significantly reduces the need for verbal position reports in equipped airspace.
CPDLC (Controller-Pilot Data Link Communications) allows text-based messages between pilots and controllers, including position reports. This system reduces radio congestion and misunderstandings, particularly in oceanic and international operations.
Despite these technologies, voice position reports remain required in certain situations:
| Situation | ADS-B/CPDLC Requirement | Voice Requirement |
|---|---|---|
| Non-radar environment | May supplement | Still required at reporting points |
| Initial contact with new controller | Provides position data | Still required for verbal confirmation |
| Emergency situations | Continues to transmit position | Required for nature of emergency |
| Equipment failures | May be unavailable | Required as backup |
Future trends in position reporting technology include:
- Further integration of voice and digital communications
- Enhanced precision of automated position reporting
- Expanded coverage in remote and oceanic areas
- Increased data sharing between aircraft systems and ATC
ADS-B and Radar Position Reporting Integration
ADS-B technology provides automated position reporting that supplements traditional voice reports. Understanding how these systems work together clarifies when voice position reports are still required even with ADS-B equipped aircraft.
ADS-B transmits position information by:
- Determining position via GPS
- Broadcasting position, altitude, speed, and aircraft ID
- Updating information typically once per second
- Providing greater accuracy than traditional radar
ADS-B Out (transmission capability) is now required in most controlled airspace in the United States. ADS-B In (reception capability) allows pilots to see other aircraft positions on cockpit displays.
Despite ADS-B capabilities, voice position reports remain required when:
- Operating in non-radar environments
- Specifically instructed by ATC
- ADS-B system failures occur
- Operating in areas without ADS-B coverage
- Transitioning between control facilities
| Environment | With ADS-B | Without ADS-B |
|---|---|---|
| Radar coverage | Minimal voice reports | Standard position reports |
| Non-radar areas | Voice reports still required | Full position reports required |
| Emergency situations | Voice reports required | Voice reports required |
ADS-B coverage limitations include:
- Ground station coverage gaps in remote areas
- Line-of-sight limitations similar to radar
- Potential GPS signal interruptions
- System outages and technical issues
International Position Reporting Standards
International flights may encounter different position reporting standards. Understanding the differences between FAA and ICAO position reporting requirements helps pilots operate safely in international airspace.
ICAO (International Civil Aviation Organization) standards form the basis for global aviation communications, but regional variations exist in how these standards are implemented. Key differences between FAA and ICAO position reporting include:
| Element | FAA Practice | ICAO Standard |
|---|---|---|
| Altitude reporting | “One zero thousand” | “Flight level one zero zero” |
| Position format | Fixes, navaids, airports | Coordinates more common |
| Phraseology | Some regional variations | Strict standardization |
| Units | Feet, nautical miles, knots | Meters, kilometers in some regions |
When operating internationally, position reports often use:
- Flight level instead of altitude in thousands of feet
- Coordinates more frequently than named fixes
- More formal, standardized phraseology
- Different measurement units in some regions
Example ICAO format position report: “Paris Control, November One Two Three Four Five, position GANOV at time one four two zero, flight level three three zero, estimating DIKEB at time one four five five, ABDAM next.”
Language considerations remain important for international operations, with English as the international aviation language, but regional accents and phraseology variations require heightened attention to communication clarity.
Oceanic and Remote Area Position Reporting
Oceanic and remote area operations have stringent position reporting requirements due to limited radar coverage and communication challenges. These specialized procedures ensure safe separation in these environments.
Oceanic position reports follow a complete format that includes:
- Aircraft identification
- Position (usually coordinates)
- Time over position (UTC/Zulu)
- Flight level
- Next position and estimated time
- Following position
- Remarks (fuel, weather deviations, etc.)
Example oceanic position report: “Gander Radio, November One Two Three Four Five, position five zero north, three zero west, time one four two zero, flight level three four zero, estimating five one north, four zero west at time one five zero five, five two north, five zero west next.”
Timing requirements for oceanic reports are strict:
- Reports must be made within 3 minutes of the scheduled reporting time
- If unable to report at the scheduled time, advise ATC as soon as possible
- When position or time estimates change by 3 minutes or more, file a revised estimate
Communication methods for oceanic reporting include:
- HF radio (long-range but variable quality)
- SATCOM (satellite communications, more reliable)
- CPDLC (data link communications)
- SELCAL (selective calling system)
During emergencies over remote areas, position reports should include:
- Most precise position possible (coordinates preferred)
- Heading and speed
- Altitude and any altitude changes
- Any visual references
- Weather conditions in your vicinity
Position Reporting Quick Reference Guide
This quick reference guide provides at-a-glance position reporting formats for each flight phase. Keep these standardized formats handy in the cockpit for consistent, compliant communications.
Ground Operations:
- Initial contact: “[Facility], [Aircraft ID], [Location on airport], with [ATIS], request [intention].”
- Hold short: “[Aircraft ID] holding short runway [number].”
- Runway crossing: “Crossing runway [number], [Aircraft ID].”
Departures:
- Towered IFR: “[Departure facility], [Aircraft ID], passing [altitude], climbing to [assigned altitude], [heading if assigned].”
- Non-towered VFR: “[Airport] Traffic, [Aircraft ID], departing runway [number], [direction] departure, [Airport].”
En-route:
- Complete position report: “[Facility], [Aircraft ID], [position] at [time], [altitude], estimating [next fix] at [time], [following fix] next.”
- VFR flight following: “[Facility], [Aircraft ID], [position], [altitude], [destination].”
Approaches:
- Initial approach contact: “[Approach facility], [Aircraft ID], [position], [altitude], with [ATIS], request [approach type].”
- Final approach: “[Aircraft ID], [fix] inbound, maintaining [altitude] until [fix].”
Common mistakes to avoid:
- Omitting aircraft identification in busy environments
- Using imprecise position references (“nearby,” “close to”)
- Reporting incorrect altitudes or mixing up altitude types
- Using non-standard phraseology
- Providing too much unnecessary information
Position Report Element Checklist by Flight Phase
This checklist organizes required position report elements by flight phase. Use it to ensure your reports contain all necessary information for each situation.
Ground Operations Checklist:
| Element | Required | Example |
|---|---|---|
| Aircraft identification | Always | “Cessna Three Four Five Six November” |
| Location on airfield | Initial contact | “at general aviation ramp” |
| ATIS information | Initial contact | “with information Delta” |
| Intentions | Initial contact | “request taxi for VFR departure to the north” |
Departure Checklist:
| Element | Required | Example |
|---|---|---|
| Aircraft identification | Always | “Cessna Three Four Five Six November” |
| Current altitude | Always | “passing two thousand” |
| Assigned/target altitude | Always | “climbing to five thousand” |
| Heading (if assigned) | When applicable | “heading zero-nine-zero” |
| Departure direction (VFR) | Non-towered | “northbound departure” |
En-route Checklist (Non-radar):
| Element | Required | Example |
|---|---|---|
| Aircraft identification | Always | “Cessna Three Four Five Six November” |
| Position | Always | “over Augusta VOR” |
| Time | Always | “at one-five-two-zero” |
| Altitude | Always | “maintaining six thousand” |
| Next fix and ETA | Always | “estimating Portland VOR at one-five-four-five” |
| Following fix | Always | “Kennebunk next” |
Approach Checklist:
| Element | Required | Example |
|---|---|---|
| Aircraft identification | Always | “Cessna Three Four Five Six November” |
| Position/fix | Always | “COHAS inbound” |
| Altitude | Always | “maintaining three thousand” |
| Approach type (initial contact) | Initial contact | “request ILS runway four-right” |
| Airport in sight | When applicable | “field in sight” |
Common Position Reporting Mistakes and How to Avoid Them
Even experienced pilots make common position reporting errors that can create confusion or compromise safety. Understanding these mistakes and how to avoid them improves your radio communications and enhances flight safety.
Mistake #1: Incomplete identification
Incorrect: “Tower, Cessna Five Six November on downwind.”
Correct: “Tower, Cessna Three Four Five Six November on downwind.”
Mistake #2: Vague position references
Incorrect: “Approach, Cessna Three Four Five Six November, near the lake.”
Correct: “Approach, Cessna Three Four Five Six November, eight miles east of Manchester VOR.”
Mistake #3: Altitude ambiguity
Incorrect: “Maintaining flight level ten thousand five hundred.”
Correct: “Maintaining one zero thousand five hundred.” (or “Flight level one zero five” if appropriate)
Mistake #4: Excessive information
Incorrect: “Center, Cessna Three Four Five Six November, we’re about 15 miles or so from Boston, around 6,500 feet, and we’d like to request flight following to Portland if that’s possible at this time.”
Correct: “Boston Center, Cessna Three Four Five Six November, 15 miles west of Boston, 6,500, request flight following to Portland.”
Mistake #5: Non-standard phraseology
Incorrect: “Tower, I’m taking off now.”
Correct: “Tower, Cessna Three Four Five Six November, ready for departure, runway one-five.”
Controllers report that the most common position reporting errors include:
- Omitting aircraft identification on subsequent calls
- Incorrect altitude reporting (especially transitioning through 10,000 feet)
- Reporting positions relative to landmarks not on aeronautical charts
- Failing to report at compulsory reporting points
- Using local terminology unfamiliar to controllers
Improving Position Report Clarity and Effectiveness
Clear, effective position reports enhance safety and reduce radio congestion. These techniques will help you communicate your position with maximum clarity and minimum confusion.
Radio technique tips:
- Think before transmitting: Organize your thoughts in the standard sequence
- Speak at moderate pace: Not too fast, not too slow
- Use consistent volume: Speak with normal voice, not louder for emphasis
- Proper microphone position: 1-2 inches from lips
- Clear enunciation: Particularly for numbers and similar-sounding letters
Pre-planning reports:
- Anticipate upcoming reporting points
- Note times and positions before reaching reporting points
- Prepare standard reports during low-workload periods
- Use shorthand notes or electronic flight logs to record information
Examples of clear vs. unclear position reports:
Unclear: “Center, uh, Cessna, um, Three Four Five Six November, we’re at, let me see, about Augusta VOR now, at, uh, one-five-two-zero, and we’re at six thousand feet, and we should be at Portland at about, let’s see, one-five-four-five or so.”
Clear: “Boston Center, Cessna Three Four Five Six November, Augusta VOR at one-five-two-zero, six thousand, estimating Portland VOR at one-five-four-five, Kennebunk next.”
In high-workload situations:
- Prioritize flying the aircraft first
- Use the most concise format appropriate for the situation
- Delay non-critical reports if necessary
- Use standard abbreviated formats when appropriate
Remember that effective position reporting is a skill that improves with practice, preparation, and consistent application of standard procedures.
| Photo | TOP RATED WALKIE TALKIES | Price |
|---|---|---|
| Retevis RT628 Walkie Talkies for Kids,Toy Gifts for 6-12 Year Old Boys Girls,Kid Gifts Walkie Talkie for Adults Outdoor Camping Hiking(Silvery 1 Pair) | Check Price On Amazon |
| Cobra ACXT545 Weather-Resistant Walkie Talkies - Rechargeable, 22 Channels, Long Range 28-Mile Two-Way Radio Set (2-Pack) | Check Price On Amazon |
| Retevis RT388 Walkie Talkies for Kids, Toys for 6 7 8 9 12 Year Old Boys, 22 CH 2 Way Radio Backlit LCD Flashlight, Blue Walkie Talkies for Boys Gifts Easter Basket Stuffers(Blue, 2 Pack) | Check Price On Amazon |
| Cobra RX680 Walkie Talkies (2-Pack) - Rugged & Splashproof Two Way Radios Long Range, IP54 Water Resistant Design, 60 Pre-Programmed Channels, Weather Alerts, Included Charging Dock (Black/Orange) | Check Price On Amazon |
| Retevis RT22 Walkie Talkies, Mini 2 Way Radio Rechargeable, VOX Handsfree, Portable, Two-Way Radios Long Range with Earpiece, for Family Road Trip Camping Hiking Skiing(2 Pack, Black) | Check Price On Amazon |
| Midland GXT1000VP4 GMRS Two-Way Radio (50 Channel, Long Range, 142 Privacy Codes, SOS, NOAA, Rechargeable Nickel Battery, Black/Silver 2-Pack) | Check Price On Amazon |
| Retevis RT628 Walkie Talkies for Kids,Toys Gifts for 6-12 Years Old Boys Girls,Long Range 2 Way Radio 22CH VOX,Birthday Gift,Family Walkie Talkie for Camping Hiking Indoor Outdoor | Check Price On Amazon |



