37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1641305 |
Time | |
Date | 201904 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SAN.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A319 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Person 1 | |
Function | Captain Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Total 8 |
Events | |
Anomaly | Deviation - Procedural Clearance Inflight Event / Encounter CFTT / CFIT |
Narrative:
On downwind abeam ksan at 5000'; given a base turn to final just outside of sayae; extended off of sayae and was in the turn to intercept final; cleared to 3800 until established on final. Armed app; descended to the crossing alt 3200 for sayae; told by ATC that we had an altitude deviation at 3400; due to the MVA altitude for that airspace. I extended off of sayae; maybe if I had extended off of okain of vydda my sa would have been better as to where 3800 would have put me in relation to final; but the controller turned me in to intercept and as far as I could see; sayae was the logical point to extend from. Had we not started our descent when we did; very likely we would have crossed sayae at 3800; 600' higher than the charted altitude and would have been very difficult to have been stable at 1000 on an already aggressive approach; (3.5 degree final.)on downwind I should have asked what approach we were being set up for; I should have just said I wanted vectors to lyndi for the full RNAV approach to 27. I wasn't given a 'cleared for the app' ; just a turn to and maintain 3800 till established; which had us way high for that part of the approach; there's very little distance between okain and sayae (1.9) and vydda and okain (2.0). When given vectors close in to final; and you're high; descending; very challenging to see exactly which point to extend off; so I took the point that appears to me that's in front of us. Even if it was just a visual. [Also] I don't recall being cleared for a visual; so I can't honestly tell what we were cleared for; we should have waited to engage the app button till established on final; at least in this scenario.
Original NASA ASRS Text
Title: A319 Captain reported momentary loss of situational awareness resulting in excursion from assigned altitude when assigned base turn to final until established on final.
Narrative: On downwind abeam KSAN at 5000'; given a base turn to final just outside of SAYAE; extended off of SAYAE and was in the turn to intercept final; cleared to 3800 until established on final. Armed app; descended to the crossing alt 3200 for SAYAE; told by ATC that we had an altitude deviation at 3400; due to the MVA altitude for that airspace. I extended off of SAYAE; maybe if I had extended off of OKAIN of VYDDA my SA would have been better as to where 3800 would have put me in relation to final; but the controller turned me in to intercept and as far as I could see; SAYAE was the logical point to extend from. Had we not started our descent when we did; very likely we would have crossed SAYAE at 3800; 600' higher than the charted altitude and would have been very difficult to have been stable at 1000 on an already aggressive approach; (3.5 degree final.)On downwind I should have asked what approach we were being set up for; I should have just said I wanted vectors to LYNDI for the full RNAV approach to 27. I wasn't given a 'cleared for the app' ; just a turn to and maintain 3800 till established; which had us way high for that part of the approach; there's very little distance between OKAIN and SAYAE (1.9) and VYDDA and OKAIN (2.0). When given vectors close in to final; and you're high; descending; very challenging to see exactly which point to extend off; so I took the point that appears to me that's in front of us. Even if it was just a visual. [Also] I don't recall being cleared for a visual; so I can't honestly tell what we were cleared for; we should have waited to engage the APP button till established on final; at least in this scenario.
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.