Welcome to the NavList Message Boards.

NavList:

A Community Devoted to the Preservation and Practice of Celestial Navigation and Other Methods of Traditional Wayfinding

Compose Your Message

Message:αβγ
Message:abc
Add Images & Files
    or...
       
    Reply
    Re: sight reduction tables
    From: Gary LaPook
    Date: 2007 Oct 02, 14:10 -0700

    Assuming 30 nm intercepts and a "cut" (difference in azimuth) of the
    perfect 90�, you will end up with an error of 8 nm. but assuming a cut
    of 120� (not perfect but common and acceptable) the error will grow to
    19 nm.  You could do another iteration if you want but how would you
    know which cases require it?
    
    (BTW, given the altitudes of three bodies and the date and time, you
    can determine your position with no idea of your dead reckoned
    position, only that you are somewhere on earth, in three or four
    iterations.)
    
    gl
    
    On Oct 2, 4:29 am, Ronald van Riet  wrote:
    > I am a relative newcomer to the celestial navigation arena so forgive
    > me if what I say has been said a zillion times before or makes no
    > sense at all, but George points out (rightly it seems) that there can
    > be large errors in azimuth with an example where the azimuth is up to
    > 15 degrees off.
    >
    > Why is that so bad? By how much does that displace the resulting LOP
    > and the fix using one or two more LOPs?
    >
    > And if you want to be more precise, why not use the new fix as the
    > assumed position for a next round of calculations? Since this AP would
    > be much nearer the actual position, an azimuth offset by 15 deg won't
    > make any significant difference.
    >
    > Then again, if we know under what circumstances the error is large,
    > why not shoot some celestial objects that do not exhibit these large
    > errors? assuming of course, that these are available.....
    >
    > Ronald
    >
    > On Oct 1, 9:59 pm, "George Huxtable" 
    > wrote:
    >
    >
    >
    > > It's when we come to calculating azimuths that Bennett's tables fall down.
    > > It's true that as long as intercepts are kept short, by a good guess at the
    > > DR position, no great precision is called for in azimuths. Bennett has
    > > claimed for his azimuth tables, in the 2003-2007 edition- "No interpolation
    > > is required, and it is one of the simplest techniques for finding azimuth
    > > with an accuracy of one or two degrees". If that claim were met in all
    > > cases, the method would be perfectly acceptable. But I will show below that
    > > in certain circumstances, it's very far from being met. To be fair, Bennett
    > > agreed, some years ago, that those claims would be modified in some way, and
    > > I hope, in the new edition, that this has been done; or better still, his
    > > azimuth methods have somehow been improved.
    >
    > > The difficulty arises because azimuths are calculated, within his table,
    > > from their sines, and for azimuths anywhere near East and West, small
    > > changes in those sines give rise to large changes in azimuth. It's
    > > compounded by the way that input to the table can be made only in integral
    > > degrees, so you have to round quantities up or down appropriately, to the
    > > nearest whole degree.
    >
    > > I will give an example of the way things can go wrong. To be fair, it isn't
    > > a typical case; I have taken a bit of trouble to hit on an example where the
    > > table goes particularly haywire. It may be a worst-case, or there may be
    > > other combinations which are equally bad, or even worse. But you will see
    > > that there's nothing strange about the numbers I have put in, which
    > > represent perfectly ordinary observations. If you have a copy of Bennett,
    > > you can try it for yourself.
    >
    > > Take a DR latitude to be N 60d 10 ', sighting a (mythical) star at dec N 55d
    > > 31', with LHA 54d 29'. Bennett's tables give an altitude of 61d 29',
    > > compared with a precisely computed value, by a different methos, of 61d
    > > 29.0. Nothing to complain about there, then.
    >
    > > Next, round those quantities to the nearest minute, and enter the azimuth
    > > calculation, with dec 56, LHA 54, producing a lookup value of 452. Look for
    > > this value at alt= 61, and rejecting the ambiguities, the result is Az =
    > > 291d. This compares with the true value, from a precise calculation, of Az =
    > > 285.1d. Such a six-degree error in azimuth is a long way out, isn't it?
    >
    > > But worse is to come.
    >
    > > Next, take marginally different values, only a few minutes different, as
    > > follows-
    >
    > > DR Lat, N 60d 25', star dec 55d 29', LHA 54d 31'. The altitude tables now
    > > give 61d 31', compared with 61d 30.8' from precise calculation. That, too is
    > > in excellent agreement.
    >
    > > But what about the azimuths, when we plug in the new rounded values, dec =
    > > 55, LHA = 55, now giving a lookup value of  469? With an altitude now
    > > rounded to 62d, the resulting azimuth is now in the band 270 to 272 degrees!
    > > But calculated precisely, by another method, the correct azimuth would be
    > > 284.7d. An immense error of 13 to 15 degrees!
    
    
    --~--~---------~--~----~------------~-------~--~----~
    To post to this group, send email to NavList@fer3.com
    To unsubscribe, send email to NavList-unsubscribe@fer3.com
    -~----------~----~----~----~------~----~------~--~---
    

       
    Reply
    Browse Files

    Drop Files

    NavList

    What is NavList?

    Join NavList

    Name:
    (please, no nicknames or handles)
    Email:
    Do you want to receive all group messages by email?
    Yes No

    You can also join by posting. Your first on-topic post automatically makes you a member.

    Posting Code

    Enter the email address associated with your NavList messages. Your posting code will be emailed to you immediately.
    Email:

    Email Settings

    Posting Code:

    Custom Index

    Subject:
    Author:
    Start date: (yyyymm dd)
    End date: (yyyymm dd)

    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site