37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 860727 |
Time | |
Date | 200911 |
Local Time Of Day | 0001-0600 |
Place | |
Locale Reference | BUR.Tower |
State Reference | CA |
Aircraft 1 | |
Make Model Name | Golden Eagle 421 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
We were operating on our alternate runway configuration due to winds with an inexperienced crew (and inexperienced feed from approach). We had a string of arrivals from the southwest (normal on this configuration); and a C421 from the southeast. Approach spun the C421 to build space but didn't descend the aircraft. Local control called to approach to ask what the plan was when the C421 came over on a 1 mile final above 3000 ft. Local control asked if he could make it down and the pilot replied 'no'. Local control called approach to get missed instructions and was told; 'it's a visual approach...keep him in the pattern'. Approach mistook the visual approach for VFR and should have given instructions. The local control said he would handle it; and started to issue vectors below the MVA. The C421 was in sight at all times as was the terrain; so it was never in danger. By the time everything was over; I realized the C421 was vectored below the MVA; but local control really had no choice; except to possibly keep the aircraft doing 360's until there was adequate spacing. Recommendation; make sure approach knows that a visual approach; while IFR; needs missed approach instructions and can not descend over 2000 ft in a mile. Remind controllers that IFR aircraft may not be vectored below the MVA.
Original NASA ASRS Text
Title: BUR Controller described event when SCT failed to provide appropriate service to an IFR inbound aircraft; transferred the traffic to the Tower and the Tower then violated MVA requirements.
Narrative: We were operating on our alternate runway configuration due to winds with an inexperienced crew (and inexperienced feed from approach). We had a string of arrivals from the southwest (normal on this configuration); and a C421 from the southeast. Approach spun the C421 to build space but didn't descend the aircraft. Local Control called to approach to ask what the plan was when the C421 came over on a 1 mile final above 3000 FT. Local Control asked if he could make it down and the pilot replied 'no'. Local Control called approach to get missed instructions and was told; 'it's a visual approach...keep him in the pattern'. Approach mistook the visual approach for VFR and should have given instructions. The Local Control said he would handle it; and started to issue vectors below the MVA. The C421 was in sight at all times as was the terrain; so it was never in danger. By the time everything was over; I realized the C421 was vectored below the MVA; but Local Control really had no choice; except to possibly keep the aircraft doing 360's until there was adequate spacing. Recommendation; make sure approach knows that a visual approach; while IFR; needs missed approach instructions and can not descend over 2000 FT in a mile. Remind controllers that IFR aircraft may not be vectored below the MVA.
Data retrieved from NASA's ASRS site as of April 2012 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.