[bvipilots] Re: Visual Approach Issue
- From: Robert Cezar <robert@xxxxxxxxxxxxxxx>
- To: bvipilots@xxxxxxxxxxxxx
- Date: Sun, 20 Apr 2014 08:10:10 -0700
Hello Jody,
The conditions for Michelle suggesting the performance of the approach
checklist are as follows:
ILS APPROACH:
Consider the airport is at 12 o'clock, the aircraft is on BASE flying 9
o'clock or 3 o'clock, and the Localizer and Glideslope are alive. Once ATC
directs us to turn 30 degrees from Final (approximately 10:30 o'clock or
1:30 o'clock respectively), Michelle will say, *"This might be a good time
to do the approach checklist."*
VISUAL APPROACH:
Consider the airport is at 12 o'clock, the aircraft is on BASE flying 9
o'clock or 3 o'clock, the distance to the airport is less than 27 miles and
the AGL (Altitude Above Ground Level) is less than the Distance to the
Airport multiplied by 333 feet. Once ATC directs us to turn 30 degrees from
Final (approximately 10:30 o'clock or 1:30 o'clock respectively), Michelle
will say, *"This might be a good time to do the approach checklist."*
NOTE 1: Considering the foregoing, if you are approaching the airport at an
altitude that exceeds 8,891 feet AGL (i.e., 27 miles * 333), Michelle will
NOT perform the visual approach.
NOTE 2: If you are less than 8,891 feet AGL, are less than 27 miles from
the airport and are on a heading that is between 10:30 o'clock and 1:30
o'clock, Michelle will say, *"This might be a good time to do the approach
checklist." *This earlier than normal execution of the approach checklist
will not adversely affect the approach - in fact, it will likely improve
the approach performance.
NOTE 3: When on BASE and ATC says, "The airport is at your 9 o'clock or 3
o'clock", IMMEDIATELY ask Michelle to perform the visual approach BEFORE
doing anything else - including responding the to ATC directive. Then*
"Acknowledge" *ATC directive, then *"Report runway in sight" *and do the
approach checklist.
NOTE 4: When flying larger jet aircraft, it's usually a good idea to
perform the approach checklist BEFORE Michelle's suggestion when on BASE -
BUT not BEFORE.
I hope this helps.
*Robert*
On Sun, Apr 20, 2014 at 7:10 AM, Jody McKinniss <jlove42010@xxxxxxxxx>wrote:
> Cool, it works now. One question: Michelle seems to want to do the
> approach list before actually turning onto final:
> 08:59:29
> Michelle said: Captain. This might be a good time to do the approach
> checklist. 08:59:30
> Michelle said: Distance to approach point, 2 miles.
> So, like a good little boy I went along with her idea and said
> "approach checklist." What ended up happening is that I didn't crash,
> but I didn't land on the runway correctly either since she hadn't yet
> made the turn for entry onto final. Advise please.
>
> On 4/20/14, Hadi Rezaei <hadirezaei@xxxxxxx> wrote:
> > Roger robert, thank you
> >
> > On 4/20/2014 2:57 AM, Robert Cezar wrote:
> >> ATTENTION: Hadi
> >>
> >> Your new version is also online.
> >>
> >> Robert
> >>
> >>
> >>
> >> On Sat, Apr 19, 2014 at 3:20 PM, Jordan Gallacher
> >> <jordanandseptember@xxxxxxxxx <mailto:jordanandseptember@xxxxxxxxx>>
> >> wrote:
> >>
> >> Okay. Will do. Thanks Robert.
> >>
> >> Jordan
> >>
> >> *From:*bvipilots-bounce@xxxxxxxxxxxxx
> >> <mailto:bvipilots-bounce@xxxxxxxxxxxxx>
> >> [mailto:bvipilots-bounce@xxxxxxxxxxxxx
> >> <mailto:bvipilots-bounce@xxxxxxxxxxxxx>] *On Behalf Of *Robert
> Cezar
> >> *Sent:* Saturday, April 19, 2014 5:20 PM
> >> *To:* bvipilots@xxxxxxxxxxxxx <mailto:bvipilots@xxxxxxxxxxxxx>
> >> *Subject:* [bvipilots] Re: Visual Approach Issue
> >>
> >> I have fixed the reported problem. Please see the Revisions
> >> section of the IYP site for details.
> >>
> >> Robert
> >>
> >> On Sat, Apr 19, 2014 at 1:15 PM, Robert Cezar
> >> <robert@xxxxxxxxxxxxxxx <mailto:robert@xxxxxxxxxxxxxxx>> wrote:
> >>
> >> Hello Jody,
> >>
> >> I will look into this and report back.
> >>
> >> Robert
> >>
> >> On Sat, Apr 19, 2014 at 8:24 AM, Jody McKinniss
> >> <jlove42010@xxxxxxxxx <mailto:jlove42010@xxxxxxxxx>> wrote:
> >>
> >> I was going to post this in the forum, but it keeps telling me "an
> >> error has occurred when I try to post it, so I will post here. I
> did
> >> the descent checklist as required by the manual, and got the
> >> following
> >> error when ready for visual approach. Relevant log below:
> >> 10:18:23
> >> Michelle said: 7000, -1900, 310
> >> 10:18:29
> >> You said: prepare to land on runway one four left
> >> 10:18:34
> >> Michelle said: Roger. I've made the course one four zero, and I
> will
> >> shortly be turning the aircraft towards the approach entry point.
> >> 10:18:37
> >> Michelle said: Airport is 18 miles.
> >> 10:18:46
> >> Michelle said: The airport is at our eleven o clock
> >> 10:18:46
> >> Michelle said: Distance to entry point, 11 miles.
> >> 10:18:51
> >> Michelle said: 6000, -1900, 300
> >> 10:18:59
> >> Michelle said: Airport is 16 miles.
> >> 10:19:13
> >> Michelle said: The airport is at our ten o clock
> >> 10:19:13
> >> Michelle said: 5000, -1900, 288
> >> 10:19:32
> >> Michelle said: Airport is 14 miles.
> >> 10:19:42
> >> Michelle said: The airport is at our ten o clock
> >> 10:19:42
> >> Michelle said: 4000, -300, 280
> >> 10:20:09
> >> Michelle said: Level at 4000
> >> 10:20:09
> >> Michelle said: Flaps 1.
> >> 10:20:13
> >> Michelle said: The descent checklist has been completed.
> >> 10:20:18
> >> Michelle said: Airport is 12 miles.
> >> 10:20:22
> >> Michelle said: The airport is at our ten o clock
> >> 10:20:23
> >> Michelle said: Captain. This might be a good time to do the
> approach
> >> checklist. 10:20:24
> >> Michelle said: Distance to approach point, 4 miles.
> >> 10:20:31
> >> You said: approach checklist
> >> 10:20:43
> >> Michelle said: Roger. We'll do the approach and landing checklists.
> >> 10:20:44
> >> Michelle said: Do you want me to assist you?
> >> I said "affirmative," and this is what resulted:
> >> 10:20:49
> >> Value: EXCEPTION: Timer2() Conversion from string "14L" to type
> >> 'Double' is not valid. 10:20:51
> >> Value: EXCEPTION: Timer2() Conversion from string "14L" to type
> >> 'Double' is not valid...
> >> (repeats)
> >> Blind and Visually impaired Pilots mailinglist
> >> //www.freelists.org/list/bvipilots
> >> To post a message to the list, send a message to
> >> bvipilots@xxxxxxxxxxxxx <mailto:bvipilots@xxxxxxxxxxxxx>
> >> To unsubscribe, send a message to
> >> bvipilots-request@xxxxxxxxxxxxx
> >> <mailto:bvipilots-request@xxxxxxxxxxxxx> and put the word
> >> unsubscribe in the subject of your message.
> >> For other options such as digest, send a message to
> >> bvipilots-request@xxxxxxxxxxxxx
> >> <mailto:bvipilots-request@xxxxxxxxxxxxx> and put the word help in
> >> the subject of your message.
> >>
> >>
> >>
> >> --
> >>
> >> AOPA Member No: 06936977
> >>
> >>
> >>
> >> --
> >>
> >> AOPA Member No: 06936977
> >>
> >>
> >>
> >>
> >> --
> >>
> >>
> >> AOPA Member No: 06936977
> >>
> >
> >
> Blind and Visually impaired Pilots mailinglist
> //www.freelists.org/list/bvipilots
> To post a message to the list, send a message to
> bvipilots@xxxxxxxxxxxxx
> To unsubscribe, send a message to
> bvipilots-request@xxxxxxxxxxxxx and put the word unsubscribe in the
> subject of your message.
> For other options such as digest, send a message to
> bvipilots-request@xxxxxxxxxxxxx and put the word help in the subject of
> your message.
>
--
AOPA Member No: 06936977
Other related posts:
