37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1317945 |
Time | |
Date | 201512 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | NCT.TRACON |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Inflight Event / Encounter CFTT / CFIT |
Narrative:
Cleared direct to parbb and maintain 4500. I slow to 210 KIAS; go to flaps 1 and I maintain 4500 to parbb. After parbb we initially turn to follow track to zolum and ATC says; direct to mitoe descend 4000. I open descend to 4000 and continue to slow to 200 because we are getting close. There's a stretch of uncomfortable silence from the controller as I feel that we need to further descend because I notice the 'profile descent donut' traveling down my pfd; and then I say to the first officer (first officer) 'give him a call; because I think he has forgotten about us; we need to descend.' at that moment ATC says 'descend to 2500.' I immediately set 2500 and open descend. Then ATC ask 'do you have the airport in sight' and we respond yes. ATC then says 'cleared visual approach runway 30.' I set 2000 for mitoe altitude and continue open descent. Some time passes then I get 'terrain; terrain;' I initiate a pull up by applying back stick; auto pilot disconnects; then 'pull up; pull up' is heard; and then silence. So; after a moment; I level the aircraft somewhere above 3000 feet. As I'm leveling and trying to understand what has happened; ATC says be careful of high terrain. First officer says yes we noticed. Because this event unsettled me for the moment I tell the first officer that I want to discontinue this approach; ask ATC for vectors. He settles me by saying 'we are just above 3000' and still on course to mitoe with plenty of room to descend to 2000'. I say 'ok;' and re-engage the auto-pilot; and proceed to a flaps 3 visual approach to runway 30 oak. Later; I ask the first officer; 'at what altitude did we get the 'terrain; terrain.' he responded at about 2800.possible reasons:I had anticipated doing a full approach and following the approach and arrival profile. It was late; and it seemed as though we were the last aircraft flying into oak. There were a few ATC silent moments. Seeing the descent profile donut travel down and out of sight of my pfd caused me to urgently descend. I used 'open descent.'I had not fully anticipated the high terrain in the area; even though the ILS approach was briefed. Who would have thought high terrain on an approach to the california coast? I will be more vigilant. Request full approach.
Original NASA ASRS Text
Title: A320 Captain reported receiving a GPWS terrain warning on a night visual approach to OAK when he lost situational and mode awareness descending in 'open descent' mode.
Narrative: Cleared direct to PARBB and maintain 4500. I slow to 210 KIAS; go to Flaps 1 and I maintain 4500 to PARBB. After PARBB we initially turn to follow track to ZOLUM and ATC says; direct to MITOE descend 4000. I open descend to 4000 and continue to slow to 200 because we are getting close. There's a stretch of uncomfortable silence from the controller as I feel that we need to further descend because I notice the 'profile descent donut' traveling down my PFD; and then I say to the First Officer (FO) 'give him a call; because I think he has forgotten about us; we need to descend.' At that moment ATC says 'descend to 2500.' I immediately set 2500 and open descend. Then ATC ask 'do you have the airport in sight' and we respond yes. ATC then says 'cleared visual approach Runway 30.' I set 2000 for MITOE altitude and continue open descent. Some time passes then I get 'Terrain; Terrain;' I initiate a pull up by applying back stick; auto pilot disconnects; then 'Pull up; Pull up' is heard; and then silence. So; after a moment; I level the aircraft somewhere above 3000 feet. As I'm leveling and trying to understand what has happened; ATC says be careful of high terrain. FO says yes we noticed. Because this event unsettled me for the moment I tell the FO that I want to discontinue this approach; ask ATC for vectors. He settles me by saying 'we are just above 3000' and still on course to MITOE with plenty of room to descend to 2000'. I say 'OK;' and re-engage the auto-pilot; and proceed to a Flaps 3 visual approach to Runway 30 OAK. Later; I ask the FO; 'at what altitude did we get the 'Terrain; Terrain.' He responded at about 2800.Possible reasons:I had anticipated doing a full approach and following the approach and arrival profile. It was late; and it seemed as though we were the last aircraft flying into OAK. There were a few ATC silent moments. Seeing the descent profile donut travel down and out of sight of my PFD caused me to urgently descend. I used 'open descent.'I had not fully anticipated the high terrain in the area; even though the ILS approach was briefed. Who would have thought high terrain on an approach to the California coast? I will be more vigilant. Request full approach.
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.