 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
ZAB center controller reported vectoring an aircraft without knowing the aircraft's altitude; which may have been below the minimum IFR altitude.
| Attributes | |
| ACN | 1509121 |
| Time | |
| Date | 201801 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZAB.ARTCC |
| State Reference | NM |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | B747 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Initial Climb |
| Route In Use | Vectors |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Person 1 | |
| Function | Enroute |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 12 |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft X called on my frequency on the ground looking for an IFR clearance. The airport is only a couple of miles into TRACON's airspace so I called them to see how we wanted to handle the departure. The filed route took the aircraft south out of his way until going northbound. I thought it would be much more efficient to go from the airport direct to their first fix. TRACON was good with that and they blocked 7;000 ft and below for the departure. The minimum IFR altitude in the area is 6;000 ft. When the aircraft finally departed; I radar identified aircraft X and immediately called traffic on an untracked; unknown VFR target; aircraft Y. Military airspace also became active and I needed to route the aircraft west and north of the airspace. I turned the aircraft left and proceeded to issue a traffic alert about the VFR traffic. Aircraft X was climbing very fast and I was not sure what altitude the aircraft was actually out of when a vector was issued. As my supervisor suggested; I will talk about this scenario in main briefing breakout so a best practice can be developed and also review rules and procedures for clearing an aircraft off the ground.
Original NASA ASRS Text
Title: ZAB Center Controller reported vectoring an aircraft without knowing the aircraft's altitude; which may have been below the Minimum IFR altitude.
Narrative: Aircraft X called on my frequency on the ground looking for an IFR clearance. The airport is only a couple of miles into TRACON's airspace so I called them to see how we wanted to handle the departure. The filed route took the aircraft south out of his way until going northbound. I thought it would be much more efficient to go from the airport direct to their first fix. TRACON was good with that and they blocked 7;000 ft and below for the departure. The Minimum IFR Altitude in the area is 6;000 ft. When the aircraft finally departed; I radar identified Aircraft X and immediately called traffic on an untracked; unknown VFR target; Aircraft Y. Military airspace also became active and I needed to route the aircraft west and north of the airspace. I turned the aircraft left and proceeded to issue a traffic alert about the VFR traffic. Aircraft X was climbing very fast and I was not sure what altitude the aircraft was actually out of when a vector was issued. As my supervisor suggested; I will talk about this scenario in main briefing breakout so a best practice can be developed and also review rules and procedures for clearing an aircraft off the ground.
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.