VFR position reporting

AIM 5-1-4 g. With Examples

For you, that would be the Airman's Information Manual, Chapter 5 Air
Traffic Prcedures, Section 1 Flight Plans, Part 4 VFR Flight Plan - VFR
Flights, paragraph g. Position Reporting. Example 1 and Example 2

BT

"Mxsmanic" wrote in message
...
BT writes:

From what you tend to know or have about flight following or position
reporting, that same book will (should) have the format for position
reporting.

I've been looking for the format, but I haven't found it thus far.

--
Transpose mxsmanic and gmail to reach me by e-mail.

BT writes:

AIM 5-1-4 g. With Examples

Found it, thank you. The examples aren't very highly codified;
perhaps there is no rigid format.

--
Transpose mxsmanic and gmail to reach me by e-mail.

why does it need to be rigid? how much more rigid can you get?
This is me..
This is where I am..
This is where I am going..


what more do you need?
BT

"Mxsmanic" wrote in message
...
BT writes:

AIM 5-1-4 g. With Examples

Found it, thank you. The examples aren't very highly codified;
perhaps there is no rigid format.

--
Transpose mxsmanic and gmail to reach me by e-mail.

BT writes:

why does it need to be rigid?

It doesn't have to be, but in information theory, the more rigid the
encoding, the greater than transfer of information. That's why the
phrasing of ATC communications is so highly conventionalized. That's
why METARs and TAFs have a highly specialized format.

--
Transpose mxsmanic and gmail to reach me by e-mail.

Mxsmanic wrote:
BT writes:

why does it need to be rigid?

It doesn't have to be, but in information theory, the more rigid the
encoding, the greater than transfer of information. That's why the
phrasing of ATC communications is so highly conventionalized. That's
why METARs and TAFs have a highly specialized format.

I believe the transmission of weather information by use of abbreviated
METAR codes originated in the days of 10 character-per-second Teletypes (or
possibly even earlier). The ASR 33 Teletype (the model I'm personally
familiar with) could only print uppercase characters. At that slow rate of
printing and usingg such a limited character set, brevity was an asset.

I first learned to program in 1973 using Teletypes as input and output
device. A nice picture of an ASR 33 teletype is he

http://www.catb.org/~esr/writings/ta...l/ch02s02.html

Jim Logajan writes:

I believe the transmission of weather information by use of abbreviated
METAR codes originated in the days of 10 character-per-second Teletypes (or
possibly even earlier). The ASR 33 Teletype (the model I'm personally
familiar with) could only print uppercase characters. At that slow rate of
printing and usingg such a limited character set, brevity was an asset.

Brevity is still an advantage today, albeit a less important one.

--
Transpose mxsmanic and gmail to reach me by e-mail.