 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier flight crew reported being vectored in area of high terrain which caused GPWS to issue warning.
| Attributes | |
| ACN | 1589506 |
| Time | |
| Date | 201810 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ROA.TRACON |
| State Reference | VA |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Initial Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Person 2 | |
| Function | Captain Pilot Flying |
| Qualification | Flight Crew Air Transport Pilot (ATP) |
| Events | |
| Anomaly | Conflict Airborne Conflict Inflight Event / Encounter CFTT / CFIT |
Narrative:
Being vectored to a visual approach runway 22 into roa; we had a terrain caution followed by a pull up and responded accordingly.GPWS announced the warning.while remaining at the assigned 4;000 feet from roa approach; we were on a left base for runway 22 when we received the terrain warning and associated pull up.I instantly disconnected autopilot and climbed the aircraft 200 feet. Although I was mainly focused on the instruments during that time; I'm confident that the warning was dismissed almost instantly once passed the highest point on the ridge being crossed.my only suggestion would be crews deliberately discuss crossing ridges at the lowest point possible at assigned ATC altitudes or opening up conversation with roanoke approach to see if we can get higher altitudes and longer vectors. I did read the previous write about the crew going into roanoke and having the same issue and this event was discussed in the cockpit well before it happened so both the captain and myself were ready to respond to the caution.
Original NASA ASRS Text
Title: Air Carrier flight crew reported being vectored in area of high terrain which caused GPWS to issue warning.
Narrative: Being vectored to a visual approach Runway 22 into ROA; we had a terrain caution followed by a pull up and responded accordingly.GPWS announced the warning.While remaining at the assigned 4;000 feet from ROA approach; we were on a left base for Runway 22 when we received the terrain warning and associated pull up.I instantly disconnected autopilot and climbed the aircraft 200 feet. Although I was mainly focused on the instruments during that time; I'm confident that the warning was dismissed almost instantly once passed the highest point on the ridge being crossed.My only suggestion would be crews deliberately discuss crossing ridges at the lowest point possible at assigned ATC altitudes or opening up conversation with Roanoke approach to see if we can get higher altitudes and longer vectors. I did read the previous write about the crew going into Roanoke and having the same issue and this event was discussed in the cockpit well before it happened so both the captain and myself were ready to respond to the caution.
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.