 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Approach controller reported vectoring an aircraft off the final approach course for sequencing placing it below the MVA.
| Attributes | |
| ACN | 1695410 |
| Time | |
| Date | 201910 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.TRACON |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Beechjet 400 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 9 |
| Events | |
| Anomaly | ATC Issue All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was working an approach sector. I had a BE40 inbound on vectors to final. I had delay vectored him to get two slow cessna aircraft in to the airport. At that time I also had a military aircraft inbound with minimum fuel that wouldn't take a speed reduction and also stated he couldn't take a very long downwind for fuel. I vectored the BE40 through final and then to a crosswind heading to delay for the military aircraft. Another aircraft was behind the BE40 that was kept inbound to follow the military aircraft. I went to coordinate the minimum fuel and no delay with tower and realized that the BE40 hadn't been turned back to downwind and was about to enter a higher 9;600 ft. MVA while being at 9;000 ft. I hung up with tower and instructed the BE40 to turn left to a heading of 300 and climb immediately to 9;600 ft. He entered the MVA block at 9;100 ft. Climbing to 9;600 ft within 1 mile of the MVA boundary. I would recommend looking over my traffic next time before coordinating with tower to make sure everything was separated to not be distracted while in communication with them.
Original NASA ASRS Text
Title: Approach Controller reported vectoring an aircraft off the final approach course for sequencing placing it below the MVA.
Narrative: I was working an approach sector. I had a BE40 inbound on vectors to final. I had delay vectored him to get two slow Cessna aircraft in to the airport. At that time I also had a military aircraft inbound with minimum fuel that wouldn't take a speed reduction and also stated he couldn't take a very long downwind for fuel. I vectored the BE40 through final and then to a crosswind heading to delay for the military aircraft. Another aircraft was behind the BE40 that was kept inbound to follow the military aircraft. I went to coordinate the minimum fuel and no delay with Tower and realized that the BE40 hadn't been turned back to downwind and was about to enter a higher 9;600 ft. MVA while being at 9;000 ft. I hung up with Tower and instructed the BE40 to turn left to a heading of 300 and climb immediately to 9;600 ft. He entered the MVA block at 9;100 ft. climbing to 9;600 ft within 1 mile of the MVA boundary. I would recommend looking over my traffic next time before coordinating with Tower to make sure everything was separated to not be distracted while in communication with them.
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.