Airway Intersections

[DanHenry]

fivestarr,

This really should be in a separate thread, but here's a stab at your location. First of all, I believe your units are in NM (nautical miles) not KM (kilometers) as you've listed.

The four ranges you provided to a 0.01 accuracy (60') don't intercect exactly so I'll go with:

N 35 24.617
W 097 00.323
1,102 MSL

That's using FalconView mission planning software that I fly with, 5 meter imagery, and Digital Terrain Elevation Data (DTED) for the elevation.

-Dan

 

[fivestarr]

Airway intersections -- Challenge

Congratulations!
You almost nailed it, my residence is just across the road to the south. You have it well within the 100 meters. The elevation is exactly right.
This challenge has sent me back to the FAR/AIM to bone up on a number of things; one of them (as you pointed out) is proper abbreviations. Yes, I meant nautical miles not kilometers. I had fixed in my brain that knots as regarding to speed should also be "knautical miles" as regarding to distance. Apologies to all who were confused by my mistake.
I commend you for being able to see through that error.
I have some other items that are surplus to my needs and may post another challenge, and pledge that I will research and carefully word it.
Send me your shipping address so that I may put your winnings in the mail.
Steve n6516r@charter.net
N35* 24.56
W97* 00.32
1103 msl

 

[DanHenry]

Thanks Steve,

I wondered why a pilot would be giving ranges in kilometers but wasn't sure until I plotted them and saw they didn't intersect. Once I switched to NM the only problem left was the level of precision in your data.

I'm an Air Force navigator and this took me back to the old days of celestial navigation when you'd plot your three star fix and then resolve your position. Boy, GPS has sure changed the world of navigation.

You didn't mention chart datum, but I'm assuming you're using WGS-84. In my area there approx a 200 meter error when comparing WGS-84 and Clarke-1866 positions.

FalconView is part of a software package called Portable Flight Planning System (or Software?, PFPS). It's used by many in the Army, Navy, AF, Marines, and some foreign military groups. It's a graphical system that allows me to flight plan, print charts and flight plans, and load a disk to upload my data to my aircraft systems. Just like your aviation GPS it's constantly updated with waypoint data. FalconView is also used inflight to provide a "moving map" display using GPS data for position. I can actually watch my aircraft taxi on 1-meter resolution imagery!

Thanks for the exercise. I'll drop you an e-mail with my info.

-Dan

 

[DanHenry]

Sorry, Duplicate post.

-Dan

 

[TinEar]

Speaking of favorites....

Location: 39-04-10.310N / 076-34-29.660W (MARYLAND)

Otherwise known as SPLAT

 

[mjw357]

I was talking to a buddy in another department and he said that Sectionals will contain an intersection only if the intersection is above a VOR/DME navaid on the ground.

Your buddy is incorrect, they show wherever airways intersect. Why would you need an intersection above a navaid?

Also, sectionals do show intersection names.

 

[Colin9690]

They have intersection names like mjw357 said, and they have arrows that point toward the navaid on the airway. :wink:

 

[Starion]

I noticed that some airway intersections and jetways cross above VORs and VORTACs.

 

[OutPost]

Intersections

Intersections are designated points, usually on an airway (chart) or used as a gateway point into a sector. Most intersections on airways are defined by either the nautical miles from two known fixes and can also incorporate a radial bearing degree from at least two radio navigational beacons, be it a VOR, or NDB. And they have 5 letter names.

In the cockpit and on the GPS computer, you can type in the 5 letter name and pull-up the intersection, with the Lat/Long coordinates in-order to fly directly to the intersection (fix) and it also can be a fix over a radio navigational station, VOR, VORTC, or NDB.

Cessna 74 Charlie....report the twin stacks for your base leg to 9 Left.....

The intersection happens to be the twin stacks, but has to be done visually and not by use of VOR Radials or coordinates.

Happy Listening
http://www.dc8.org/store/bertrand/videos.php

 

[inigo88]

Cessna 74 Charlie....report the twin stacks for your base leg to 9 Left.....

The intersection happens to be the twin stacks, but has to be done visually and not by use of VOR Radials or coordinates.

You have confused intersections with VFR reporting points. On a sectional aeronautical chart an intersection is a point in which two blue lines with arrows at the end cross (the arrows point toward their respective facilities - usually VORs). On an IFR low altitude en-route chart, intersections appear as white triangles but they signify the same thing.

You are referring to VFR reporting points. On sectional aeronautical charts and terminal area charts they appear as a magenta flag with black text explaining what the reporting point is (i.e. the twin stacks in your example, a golf course, large water tank... etc.). These are visual waypoints only and not used for IFR navigation like intersections are.

-Inigo

 

[inigo88]

I have several favorite intersections, and they have to be read in sequence. They are all featured on the "RNAV (GPS) RWY 16" instrument approach to the Pease Int'l Tradeport in Portsmouth, New Hampshire. Here it is: http://204.108.4.16/d-tpp/0507/00678R16.PDF

Now, I'm from california and I've never been to NH, but this was sent to me by some friends because it single-handedly proves that the FAA DOES have a sense of humor. For those of you who aren't instrument rated pilots or have never seen an instrument approach procedure before I'll try and elaborate. The pilot will most likely start the approach from the initial approach fix (IAF), the fix on the top left. From there follow the arrows down to the runway. FAF stands for Final Approach Fix, the MAP over the end of the runway stands for Missed Approach Point (should the pilot not see the runway by this point due to weather they would have to fly the missed approach), and should the pilot go missed they would proceed down to the fix on the bottom right of the chart and enter a holding pattern (thats what the race-track with the dotted lines is).

Here's the approach!!!

ITAWT
ITAWA
PUDYE
TTATT (and, should the pilot go missed approach)
IDEED !

:lol: :lol: :lol:

And if that wasn't funny enough, the other initial approach fix is SATAN! That in itself is funny, but then fly the approach from there:

SATAN ITAWA PUDYE TTATT IDEED !

I hope you guys got as much of a kick out of that as I did. :twisted: :twisted: :lol: :lol: :lol:

-Inigo

 

[OutPost]

VFR Reporting Points

You're right about that....I haven't flown anything VFR in a very long time :?

Thanks for correcting me.....can I NOW get vectors PLEASE????