I have a dumb new pilot question re best practices for changing VFR altitudes when making a course change while on flight following.
Yesterday I flew from French Valley (F70) to John Wayne (SNA) via Oceanside.
As I turned a little right toward Oceanside, and continued on, I began to descend from 5,500 to 4,500 for the new course and, ultimately, for the 303 course. The controller came on and seemed a little miffed.
I though the descent was expected, if not mandatory, based on the magnetic course of our next leg and his reference to 4,500, but I guess not.
What is best practice for working with approach when turning on a course that dictates a different VFR altitude?
Should I always request an altitude change and make sure they’re good with it before beginning?
Is it OK to stay at an odd-plus-500 altitude while already on an even-plus-500 course while waiting to get a word in?
A minor issue I suppose, but seems like a little catch-22.
Thanks!
Yesterday I flew from French Valley (F70) to John Wayne (SNA) via Oceanside.
- F70 to Oceanside is a course of 169 degrees magnetic – so above 3000 AGL, the appropriate VFR altitudes are odd thousands plus 500.
- Oceanside toward SNA, along the cost, is a course of 303 degrees magnetic – so VFR altitudes are even thousands plus 500.
As I turned a little right toward Oceanside, and continued on, I began to descend from 5,500 to 4,500 for the new course and, ultimately, for the 303 course. The controller came on and seemed a little miffed.
I though the descent was expected, if not mandatory, based on the magnetic course of our next leg and his reference to 4,500, but I guess not.
What is best practice for working with approach when turning on a course that dictates a different VFR altitude?
Should I always request an altitude change and make sure they’re good with it before beginning?
Is it OK to stay at an odd-plus-500 altitude while already on an even-plus-500 course while waiting to get a word in?
A minor issue I suppose, but seems like a little catch-22.
Thanks!