37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1321886 |
Time | |
Date | 201512 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | VNY.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft High Wing 1 Eng Fixed Gear |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | None |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Private |
Experience | Flight Crew Last 90 Days 3 Flight Crew Total 100 Flight Crew Type 5 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I was flying around the edge of the valley outside but just west of the vny class D and bur class C (near the santa susana pass) after taking off from vny. On approach to vny for landing I was informed that I had been in the way of the bur ILS approach while flying around the area (which I had not realized since I was outside of the class C and D - I had continued listening on the vny tower frequency but didn't hear anything regarding an issue so I assumed there wasn't one). By the time I was told that I had been disrupting the approach path into bur (on contacting the vny tower to return for landing) I was already descending to return to vny and continued the descent and entered the vny D as soon as possible. Since there weren't any explicit airspace issues and I am a pilot new to the airport (and still fairly new pilot in general); I didn't realize that I had been doing anything disruptive to normal air traffic operations. (On landing; since the ground frequency was not especially busy; I confirmed with the ground controller that I hadn't violated any airspace; just been accidentally disruptive; and I apologized for the annoyance and lack of knowledge.)I don't think this is necessarily a safety issue since non-IFR-rated pilots wouldn't be flying in IMC (when I assume ILS approaches are most critical). I don't know if there's much to be done to prevent similar issues in the future; but since it does disrupt normal traffic flow it could be worth trying to raise awareness of approach procedures at class C and D airports (and the fact that they do extend beyond the boundaries of the airspace) amongst student and non-IFR-rated pilots (since unsuspecting pilots can keep aircraft in the way of an approach without ever realizing the issue or actually violating any airspace - not causing a safety issue but still creating an operational challenge). I know that the IFR routes are printed on the tac; but with all the clutter on the charts and the fact that the nature and importance of instrument procedures for scheduled air operations aren't really mentioned at all during private pilot training their importance could be easily overlooked.
Original NASA ASRS Text
Title: Aircraft operating approximately 5 miles West of VNY at altitudes around 5000 feet; while clear of VNY class D and BUR class C was advised by VNY Tower they had a potentially caused a conflict with aircraft flying the ILS/LOC Z Runway 8 BUR.
Narrative: I was flying around the edge of the valley outside but just west of the VNY Class D and BUR Class C (near the Santa Susana Pass) after taking off from VNY. On approach to VNY for landing I was informed that I had been in the way of the BUR ILS approach while flying around the area (which I had not realized since I was outside of the class C and D - I had continued listening on the VNY tower frequency but didn't hear anything regarding an issue so I assumed there wasn't one). By the time I was told that I had been disrupting the approach path into BUR (on contacting the VNY tower to return for landing) I was already descending to return to VNY and continued the descent and entered the VNY D as soon as possible. Since there weren't any explicit airspace issues and I am a pilot new to the airport (and still fairly new pilot in general); I didn't realize that I had been doing anything disruptive to normal air traffic operations. (On landing; since the ground frequency was not especially busy; I confirmed with the ground controller that I hadn't violated any airspace; just been accidentally disruptive; and I apologized for the annoyance and lack of knowledge.)I don't think this is necessarily a safety issue since non-IFR-rated pilots wouldn't be flying in IMC (when I assume ILS approaches are most critical). I don't know if there's much to be done to prevent similar issues in the future; but since it does disrupt normal traffic flow it could be worth trying to raise awareness of approach procedures at class C and D airports (and the fact that they do extend beyond the boundaries of the airspace) amongst student and non-IFR-rated pilots (since unsuspecting pilots can keep aircraft in the way of an approach without ever realizing the issue or actually violating any airspace - not causing a safety issue but still creating an operational challenge). I know that the IFR routes are printed on the TAC; but with all the clutter on the charts and the fact that the nature and importance of instrument procedures for scheduled air operations aren't really mentioned at all during private pilot training their importance could be easily overlooked.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.