A aviation & planes forum. AviationBanter

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.

Go Back   Home » AviationBanter forum » rec.aviation newsgroups » Piloting
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

x-country solo



 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #10  
Old December 10th 03, 04:04 AM
Judah
external usenet poster
 
Posts: n/a
Default

I'm not sure I can offer much in the way of advice. I think this kinda
thing happens periodically, and it's not the end of the world. Especially
(having read ahead) between BDR and HVN (and possibly GON, too)...

The one comment I would make is that the fact that they reported no radar
contact, IMHO, is not enough to justify cancelling the approach (or
anywhere near "unfathomable" as you describe). Had they said "Radar
Contact, 9 miles East" when you thought you were entering the pattern, I
might have been more inclined to ask for immediate help...

Mistakes happen. Those are the kinds of things that you learn from. No one
was hurt, and I'd bet you won't have any serious negative repurcussions to
your license...

The only thing I would have done differently, though is that I would have
told the instructor about the screw up. If nothing else, he might have
taken the time to review your planning and helped you learn from the
situation.



"Joe Johnson" wrote in
m:

Scenario: student pilot on x-country solo. About 50hrs.

Planning went fine. One long outbound leg (to satisfy the FARs) and
two shorter inbound legs to fulfill the three landings requirement.

Outbound leg: went great. Course maintained and all visual landmarks
nailed, within a minute of expected time. Landed, got logbook signed,
took off on 1st inbound leg.

First inbound leg was to a class D field close to home (call it ABC);
VOR on field. Dialed in the ABC VOR and looked for visual checkpoints.
Instead, approached another class D field nearby (call it XYZ). Not
to make excuses, but ABC and XYZ actually have some geographic
similarities: distance & direction from towns of about the same size,
as well as similar relation to highways and bodies of water, etc). The
visual checkpoints enroute were also close to each other. However,
student ignored two key pieces of evidence that wrong field was being
approached:

--ABC tower reported no radar contact (why student continued approach
to XYZ is therefore unfathomable).
--VOR indicated progressive deviation from course (also not
surprising).

Mistake discovered near XYZ pattern (runways obviously didn't match).
ABC tower (still in radio contact) notified. Then XYZ tower contacted,
mistake acknowledged, and profuse apologies offered. (No mention
either way of violation for busting the XYZ class D airspace.
Student's main concern is actually to learn from this error, violation
or no).

Trip continued to ABC as planned and on to home. Congratulations
offered for completing x-country solo. No mention of error by student
or instructor.

Suggestions solicited & greatly appreciated...

 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Cross country time clyde woempner Owning 5 February 2nd 05 10:36 PM
Please Someone Invade My Country Pechs1 Naval Aviation 0 May 25th 04 02:25 PM
"I Want To FLY!"-(Youth) My store to raise funds for flying lessons Curtl33 General Aviation 7 January 9th 04 11:35 PM
US cross country flight S Narayan Instrument Flight Rules 0 January 7th 04 02:58 PM
American Slaves Grantland Military Aviation 3 September 29th 03 04:37 AM


All times are GMT +1. The time now is 06:08 AM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright ©2004-2025 AviationBanter.
The comments are property of their posters.