37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1709566 |
Time | |
Date | 201912 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ROA.Airport |
State Reference | VA |
Environment | |
Flight Conditions | VMC |
Light | Night |
Aircraft 1 | |
Make Model Name | Medium Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Approach |
Flight Plan | IFR |
Component | |
Aircraft Component | GPWS |
Person 1 | |
Function | Captain Check Pilot Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 192 Flight Crew Total 3955 Flight Crew Type 1452 |
Person 2 | |
Function | Pilot Flying First Officer |
Qualification | Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Events | |
Anomaly | ATC Issue All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
On our decent into roa we got a 'terrain pull up message.' we were being vectored on to final for runway 6 at 5;200 MSL. It appeared that the controller was vectoring us towards ramke a fix on the lda. We briefed the highest terrain on the approach which was 4;011 MSL and was just to the south of ramke. I asked for a vector that would give us more time to get set up on the approach; avoiding that obstacle and making it so we could do a much shallower approach into the valley. It was a very clear night with a very bright moon which was reflecting light off of the snow on top of the mountains. With the terrain in sight and just passing over the highest part of the mountain we called the airport in sight. The captain in training started a very slow decent at probably -100 to -300 feet per minute. As soon as he did we got the 'terrain pull up' aural message. We immediately did an egpws escape maneuver which turned off the terrain message immediately. We advised ATC and they advised us to climb to 6;000 on a heading 330. I requested a full lda for the second approach and we got in just fine.while we had briefed our entry onto the approach extensively the aircraft warning made us react.the cause must have been how we were entering the approach with the mountainous terrain.performed egpws maneuver. I should have requested the full lda in the first place and avoided any chance of needing to do an escape maneuver. Even though we had great visibility we should have just added the extra 3 minutes and done the approach. Upon our escape maneuver I advised ATC. I also told ATC that this [model of] plane seems to have a very sensitive egpws in my experience and in the experience of other people I have talked to. Hoping to help out future controllers and crews avoid this problem I pointed out that we were basically vectored at the highest point on the approach chart. It would not be easy to descend on the approach while remaining stable where our initial heading had us going. After we landed and got to the hotel I received a call from maintenance wondering if I had written anything up as ATC had advised them that the plane was broken. I think they mistook me telling them this model of aircraft as a whole as me telling them it was just that plane that had the issue. They never did issue a low terrain alert which thinking back may have been a reason they thought it could be that plane. Again in the future I will just do the full lda approach.
Original NASA ASRS Text
Title: Air Carrier flight crew reported receiving a terrain warning inbound to ROA.
Narrative: On our decent into ROA we got a 'Terrain pull up message.' We were being vectored on to final for Runway 6 at 5;200 MSL. It appeared that the controller was vectoring us towards RAMKE a fix on the LDA. We briefed the highest terrain on the approach which was 4;011 MSL and was just to the south of RAMKE. I asked for a vector that would give us more time to get set up on the approach; avoiding that obstacle and making it so we could do a much shallower approach into the valley. It was a very clear night with a very bright moon which was reflecting light off of the snow on top of the mountains. With the terrain in sight and just passing over the highest part of the mountain we called the airport in sight. The Captain in training started a very slow decent at probably -100 to -300 feet per minute. As soon as he did we got the 'Terrain pull up' aural message. We immediately did an EGPWS escape maneuver which turned off the terrain message immediately. We advised ATC and they advised us to climb to 6;000 on a heading 330. I requested a full LDA for the second approach and we got in just fine.While we had briefed our entry onto the approach extensively the aircraft warning made us react.The cause must have been how we were entering the approach with the mountainous terrain.Performed EGPWS maneuver. I should have requested the full LDA in the first place and avoided any chance of needing to do an escape maneuver. Even though we had great visibility we should have just added the extra 3 minutes and done the approach. Upon our escape maneuver I advised ATC. I also told ATC that this [model of] plane seems to have a very sensitive EGPWS in my experience and in the experience of other people I have talked to. Hoping to help out future controllers and crews avoid this problem I pointed out that we were basically vectored at the highest point on the approach chart. It would not be easy to descend on the approach while remaining stable where our initial heading had us going. After we landed and got to the hotel I received a call from Maintenance wondering if I had written anything up as ATC had advised them that the plane was broken. I think they mistook me telling them this model of aircraft as a whole as me telling them it was just that plane that had the issue. They never did issue a low terrain alert which thinking back may have been a reason they thought it could be that plane. Again in the future I will just do the full LDA 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.