It wasn’t an inference, it was a statement, and one that doesn’t make any sense.
Cross-country frustrations
- Thread starter mryan75
- Start date
Yeah it’s funny, it was the same for me and were only talking 10-11 years ago.
Mxfarm
Line Up and Wait
glad you’ve never encountered those folks then
elvisAteMySandwich
Pre-takeoff checklist
- Joined
- Jul 23, 2020
- Messages
- 136
- Display Name
Display name:
elvisAteMySandwich
Pilotage and dead reckoning worked out for me because my CFI drilled it into my head. I made it within 5 nm of the destination airport and then they started vectoring me to the right due to too much traffic in the pattern. Felt like forever. Finally, tower says turn towards the airport and I don't know where it is. I start turning left towards where I think it should be ... keep turning and then finally relief when I spot it. Didn't use foreflight or else that whole scenario would have been a lot easier.
This thread has resulted in interesting visits to my first log book.
PPL solo cross country built up fast. Times are decimal tachometer times. 1960 Cessna with a fresh engine, cruised at 95 Knots.
1.0 tt
2.3 tt
3.3 tt
2.7 tt
9.3 Total time on cross country, solo.
No airport visited twice. Control tower airports avoided, as the Omnigator had only 3 crystals.
Solid state Nav Com installed shortly before the check ride, which made using the VOR navigation more accessible. The requisite flight into a control tower airport was much easier with digital selection of comm. frequencies.
The University of Virginia runway was hard to find, as it was simply a large lawn, no airplanes on site at Monticello. I walked up to the mansion to get someone to sign my logbook to confirm that I had landed there.
All but my first cross country went further than 100 NM from College Park, and included Virginia, Maryland, and Delaware.
The popular long cross country from KCGS was Ocean City. My instructor did not like it, as he said it allowed really sloppy navigation, just fly on an approximate heading until you came to the ocean, and if there is a coastal highway, turn south. Just dunes, turn north. At the city of Ocean City, look SW, and there is the airport.
PPL solo cross country built up fast. Times are decimal tachometer times. 1960 Cessna with a fresh engine, cruised at 95 Knots.
1.0 tt
2.3 tt
3.3 tt
2.7 tt
9.3 Total time on cross country, solo.
No airport visited twice. Control tower airports avoided, as the Omnigator had only 3 crystals.
Solid state Nav Com installed shortly before the check ride, which made using the VOR navigation more accessible. The requisite flight into a control tower airport was much easier with digital selection of comm. frequencies.
The University of Virginia runway was hard to find, as it was simply a large lawn, no airplanes on site at Monticello. I walked up to the mansion to get someone to sign my logbook to confirm that I had landed there.
All but my first cross country went further than 100 NM from College Park, and included Virginia, Maryland, and Delaware.
The popular long cross country from KCGS was Ocean City. My instructor did not like it, as he said it allowed really sloppy navigation, just fly on an approximate heading until you came to the ocean, and if there is a coastal highway, turn south. Just dunes, turn north. At the city of Ocean City, look SW, and there is the airport.
THIS! These things aren't found in handbooks nor are they often taught in primary training. The longer cross-country trips are good times to explore the aircraft's systems and avionics as well. I read up and played with a Garmin 430 simulator, but exploring it on long cross countries is where I understood it. Same for the crusty KAP140.
PaulS
Touchdown! Greaser!
Remember, it's always ok to say "I lost the airport, could you give me a vector. "
MauleSkinner
Touchdown! Greaser!
As well as “Cessna 2345, Student Pilot.”