37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1408326 |
Time | |
Date | 201612 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | D10.TRACON |
State Reference | TX |
Aircraft 1 | |
Make Model Name | Light Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Approach Instructor |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 22.0 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Inflight Event / Encounter CFTT / CFIT |
Narrative:
I was providing training on dallas south when flight data physically came over to request an IFR release off for aircraft X. The trainee gave runway heading and 3000 feet for the release. What he failed to see; nor did flight data mention it; was that aircraft X was departing [on a runway in a north direction]. All other airports in the area were in a south flow. The departure strip did show aircraft X departing runway 36. Those departure instructions enter into a 3500 minimum vectoring altitude. As soon as I saw aircraft X acquire on the radar display north of [the departure airport]; I informed the trainee that those departure instructions do not work and to turn aircraft X eastbound away from the obstacles.I should have looked at the strip myself. But a verbal reminder from flight data that this departure was opposite all other flows would have gone a long way in preventing this situation.
Original NASA ASRS Text
Title: D10 TRACON Controller reported not noticing a trainee released a departure with an altitude below the Minimum Vectoring Altitude.
Narrative: I was providing training on Dallas South when Flight Data physically came over to request an IFR release off for Aircraft X. The trainee gave Runway heading and 3000 feet for the release. What he failed to see; nor did Flight Data mention it; was that Aircraft X was departing [on a Runway in a north direction]. All other airports in the area were in a South flow. The departure strip did show Aircraft X departing Runway 36. Those departure instructions enter into a 3500 Minimum Vectoring Altitude. As soon as I saw Aircraft X acquire on the radar display north of [the departure airport]; I informed the Trainee that those departure instructions do not work and to turn Aircraft X eastbound away from the obstacles.I should have looked at the strip myself. But a verbal reminder from Flight Data that this departure was opposite all other flows would have gone a long way in preventing this situation.
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.