![]() |
If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
|
#1
|
|||
|
|||
![]()
Gary Drescher wrote:
"Sam Spade" wrote in message ... Gary Drescher wrote: Right, but if NACO wants to say "LOC only" it should be for a separate specification of 1800', not for the (sole) one that's designated as the intercept altitude. For example, in SWF ILS 9, there's a 2100' intercept altitude, and separately from that there's a minimum altitude of 2100' specified for the approach segment leading up to the OM; the latter altitude is marked "LOC only". http://www.naco.faa.gov/d-tpp/0610/00450I9.PDF So the SWF chart seems right, but not the ASH chart. That chart is wrong, too. Ok, but at the SWF chart makes sense. It's wrong only in that the extra, LOC-only altitude is superfluous. --Gary Why does it make sense? |
#2
|
|||
|
|||
![]()
"Sam Spade" wrote in message
... Gary Drescher wrote: "Sam Spade" wrote in message ... Gary Drescher wrote: Right, but if NACO wants to say "LOC only" it should be for a separate specification of 1800', not for the (sole) one that's designated as the intercept altitude. For example, in SWF ILS 9, there's a 2100' intercept altitude, and separately from that there's a minimum altitude of 2100' specified for the approach segment leading up to the OM; the latter altitude is marked "LOC only". http://www.naco.faa.gov/d-tpp/0610/00450I9.PDF So the SWF chart seems right, but not the ASH chart. That chart is wrong, too. Ok, but at least the SWF chart makes sense. It's wrong only in that the extra, LOC-only altitude is superfluous. Why does it make sense? Because the chart has two altitude designations, and one of those designations applies only to LOC approaches (and is thus to be ignored when flying an ILS approach). It's just that the LOC-only altitude is superfluous in this case, because the (identical, in this case) GS-intercept altitude already serves as the LOC-approach altitude too (unless otherwise noted). --Gary |
#3
|
|||
|
|||
![]()
Gary Drescher wrote:
"Sam Spade" wrote in message ... Gary Drescher wrote: "Sam Spade" wrote in message . .. Gary Drescher wrote: Right, but if NACO wants to say "LOC only" it should be for a separate specification of 1800', not for the (sole) one that's designated as the intercept altitude. For example, in SWF ILS 9, there's a 2100' intercept altitude, and separately from that there's a minimum altitude of 2100' specified for the approach segment leading up to the OM; the latter altitude is marked "LOC only". http://www.naco.faa.gov/d-tpp/0610/00450I9.PDF So the SWF chart seems right, but not the ASH chart. That chart is wrong, too. Ok, but at least the SWF chart makes sense. It's wrong only in that the extra, LOC-only altitude is superfluous. Why does it make sense? Because the chart has two altitude designations, and one of those designations applies only to LOC approaches (and is thus to be ignored when flying an ILS approach). It's just that the LOC-only altitude is superfluous in this case, because the (identical, in this case) GS-intercept altitude already serves as the LOC-approach altitude too (unless otherwise noted). --Gary But, the two altitude designations when they are the same is incorrect, redundant, and has the potential for some confusion. |
#4
|
|||
|
|||
![]()
"Sam Spade" wrote in message
... But, the two altitude designations when they are the same is incorrect, redundant, and has the potential for some confusion. I agree that it's redundant, confusing, contrary to the chart-design rules, and shouldn't be done. My only point is that at least nothing in the SWF ILS 9 chart is overtly false (whereas the LOC-only annotation for the GS-intercept altitude in the ASH ILS 14 chart is indeed false; if it were true, there'd be no specified GS-intercept altitude for the ILS approach). --Gary |
#5
|
|||
|
|||
![]()
Gary Drescher wrote:
"Sam Spade" wrote in message ... But, the two altitude designations when they are the same is incorrect, redundant, and has the potential for some confusion. I agree that it's redundant, confusing, contrary to the chart-design rules, and shouldn't be done. My only point is that at least nothing in the SWF ILS 9 chart is overtly false (whereas the LOC-only annotation for the GS-intercept altitude in the ASH ILS 14 chart is indeed false; if it were true, there'd be no specified GS-intercept altitude for the ILS approach). --Gary Yes, one is bad, the other is worse. ;-) |
Thread Tools | |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Air Force One Had to Intercept Some Inadvertent Flyers / How? | Rick Umali | Piloting | 29 | February 15th 06 04:40 AM |
Parachute fails to save SR-22 | Capt.Doug | Piloting | 72 | February 10th 05 05:14 AM |
Pressure Altitude and Terminology | Icebound | Piloting | 0 | November 27th 04 09:14 PM |
GPS Altitude with WAAS | Phil Verghese | Instrument Flight Rules | 42 | October 5th 03 12:39 AM |
GPS Altitude with WAAS | Phil Verghese | Piloting | 38 | October 5th 03 12:39 AM |