Menu
▾
▴
#33 localizer beam
Originally created by: pedromor... (code.google.com)@gmail.com
Originally owned by: g...@av8n.com
According to ICAO, the localizer beam is supposed to be designed to be 210
meters wide at the threshold. Reference: http://dcaa.slv.dk:8000/icaodocs/.
Saying the same thing another way, the US AIM expresses this as 700 feet
wide, or ±350 feet if you prefer to think of it that way. There are
additional complexities, including a maximum pegged at 6 degrees total
width.
That means that as the runway length varies from (say) 6000 ft to 15000 ft,
the localizer varies from more than 6 degrees wide to less than 0.3 degrees
wide.
A lot of non-experts claim the CDI sensitivity is half a degree per dot,
i.e. four times as sensitive as a VOR. That is equivalent to saying the
localizer as a whole is 5 degrees wide. This might serve as a ballpark
approximation, but it is nowhere near exact.
As of 1.9.0, navradio.cxx knows nothing of this. It says:
// According to Robin Peel, the ILS is 4x more
// sensitive than a vor
r *= 4.0;
Again, this is a rough approximation, but nothing beyond that.
denker 22F
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: pedromor... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: New
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
This should be fixed in CVS / 2.0.0, I merged the relevant patches from John Denker several months ago.
Obviously confirmation would be good.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: pedromor... (code.google.com)@gmail.com
(No comment was entered for this change.)
Owner: g...@av8n.com
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: pedromor... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Accepted
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: g...@av8n.com
(No comment was entered for this change.)
Status: Verified
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: g...@av8n.com
This should be considered "verified" but I'm going to mark it as
"fixed".
That's because of a bug in the bug-tracker: verified bugs just
disappear. Fixed bugs show up on the list of fixed bugs.
Status: Fixed
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Temp
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Fixed
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gijsrooy
Fixed as of 2.0.0, so Milestone-2.0.0
Labels: Milestone-2.0.0