Answer to Last Week’s (Oct. 19) AVsavvy Question

> | October 26, 2012 | 0 Comments
Print Friendly, PDF & Email

In last Friday’s AVsavvy question, we showed you a flight schedule and some airport information and asked you to find the error.

IMPORTANT: If you haven’t yet participated, YOU CAN STILL TURN BACK NOW AND TEST YOUR SKILLS.

Below is the answer and explanation. Thank you to everyone who participated. We are happy to report a majority of you got it right. J

Answer 1. The aircraft can operate in VFR airspace at F/L 290 only in certain areas within Italian airspace
Correct. As per ICAO Annex 02, Chapter 4, paragraph 4.5, there are certain restrictions in order to grant this type of flight and it must have ENAC RVSM approval.

Answer 2. The aircraft can operate in VFR airspace at F/L 290 in Italian airspace only for daytime operations
Incorrect. The regulation doesn’t make a stipulation on time of flight.

Answer 3. The aircraft can’t operate VFR at F/L 290 in Italian airspace
Incorrect. As per ICAO Annex 02, Chapter 4, paragraph 4.5, it may be possible to conduct this type of flight, but there are certain restrictions in order to grant it and it must have ENAC RVSM approval.

Answer 4. There are no issues with operating VFR at F/L 290 in Italian airspace
Incorrect. Per ICAO Annex 02, Chapter 4, paragraph 4.5, it may be possible to conduct this type of flight, but there are certain restrictions in order to grant it and it must have ENAC RVSM approval.

Questions about this week’s AVsavvy question? Ask us in the comments area below.

Introducing uvGO. Now you can manage all of your missions in one, easy view.

Tags:

Category : Q&A

Related Posts

About

Print Friendly, PDF & Email

This is a group account for the people busily trying to make this blog the best it can be for you and the rest of the business-aviation community. If you have questions or comments about this blog, you can reach us at operationalinsight@univ-wea.com.

Operational Insight is a moderated blog.
Before adding your comments, please read our Comment Policy.