37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1501696 |
Time | |
Date | 201712 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | VNY.Airport |
State Reference | CA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Flight Phase | Final Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Instrument Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 70 Flight Crew Total 5400 Flight Crew Type 50 |
Events | |
Anomaly | Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 6000 Vertical 0 |
Narrative:
While flying the ILS (Z or Y) 16R to vny; we received a TA. We were already cleared for the approach in VFR conditions. We were told to maintain our current altitude by approach control when they realized there was a traffic conflict (we may have been with tower at this point; but I am fairly certain we were still with approach). There was VFR traffic at our altitude very close to furry on the approach. It appeared to be a single engine cessna about 1 mile or so away from our position. I do not believe that the pilot was talking to anyone. This has happened to me on several other occasions going into vny. For some reason; VFR traffic likes to fly around in that area. It is a bad area to fly without talking to anyone at that altitude with the traffic going into vny. It is my opinion that the FAA needs to reevaluate this airspace as it could eventually lead to a more serious traffic conflict. It already causes conflict for the pilots and ATC when these events occur. It would be in everyone's best interest to make it mandatory for pilots flying in that area to talk to someone and file a flight plan. Possibly change the airspace to have the approach in protected (extend class C or D) airspace. The current VFR chart shows a class east extension out towards that area. Also; educating pilots in that area or making it mandatory for VFR pilots to take a training course on the southern california area; as in the dc sfra; before operating in this area.
Original NASA ASRS Text
Title: A CL604 Captain reported an airborne conflict after receiving clearance for an ILS approach. The reporting party stated that the airspace is poorly designed to protect the ILS approach and should be reviewed.
Narrative: While flying the ILS (Z or Y) 16R to VNY; we received a TA. We were already cleared for the approach in VFR conditions. We were told to maintain our current altitude by approach control when they realized there was a traffic conflict (We may have been with tower at this point; but I am fairly certain we were still with approach). There was VFR traffic at our altitude very close to FURRY on the approach. It appeared to be a single engine Cessna about 1 mile or so away from our position. I do not believe that the pilot was talking to anyone. This has happened to me on several other occasions going into VNY. For some reason; VFR traffic likes to fly around in that area. It is a bad area to fly without talking to anyone at that altitude with the traffic going into VNY. It is my opinion that the FAA needs to reevaluate this airspace as it could eventually lead to a more serious traffic conflict. It already causes conflict for the pilots and ATC when these events occur. It would be in everyone's best interest to make it mandatory for pilots flying in that area to talk to someone and file a flight plan. Possibly change the airspace to have the approach in protected (extend Class C or D) airspace. The current VFR chart shows a Class E extension out towards that area. Also; educating pilots in that area or making it mandatory for VFR pilots to take a training course on the Southern California area; as in the DC SFRA; before operating in this area.
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.