37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1232457 |
Time | |
Date | 201412 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ASE.Airport |
State Reference | CO |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | BAe 125 Series 800 |
Operating Under FAR Part | Part 135 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Check Pilot First Officer |
Qualification | Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 50 Flight Crew Total 5000 Flight Crew Type 1500 |
Events | |
Anomaly | Deviation - Procedural Published Material / Policy Inflight Event / Encounter Weather / Turbulence Inflight Event / Encounter CFTT / CFIT |
Miss Distance | Horizontal 2000 Vertical 500 |
Narrative:
The leg was a passenger leg to ase and the weather initially was overcast 3;500 feet. We initiated the approach; descended to our minimums which are 3;100 feet; but most likely due to the slow rate of descent; we reached the missed approach point without breaking out. I called for the missed approach; which we executed; and we went out to hold. I queried ATC to see if the next aircraft made it in; and if so; what he reported the bases to be; and they said bases were still 3;500 feet. At this point we asked for a second approach; fully configured by dbl; and initiated the approach. The weather had almost completely blown through at this point and we had a visual of the field probably about 9 miles out. The pilot flying asked if he could descend to which I informed him 'a little bit' as we were still a couple of hundred feet above the published minimums for the approach. However; the flying pilot began a rapid descent and I told him to check his descent. He replied by saying he had the runway in sight and didn't want to pop back into the clouds; but I didn't see that there were any clouds above us; and I knew we needed to comply with the approach minimums even though we had a visual of the runway. The flying pilot continued to descend even after I told him to check his descent which resulted in a GPWS warning for terrain. At this same time; the tower called and asked us to immediately check our altitude as they were reporting that we were getting too close to the terrain. I informed the tower that we had a visual on the mountains and the runway; but I was very uncomfortable that the flying pilot decided to descend excessively for some reason. We landed without any further issues. The flying pilot is a fairly new pilot with our company; although he has a good deal of experience in the airplane. One of the reasons I was flying with him that day was to observe how he did flying into a mountainous airport. As the non-flying pilot; I was there to assist him with the approach and make sure everything was set up and executed correctly and on time. I believe I made a mistake when I did not strongly verbalize the minimum altitudes while directing him to arrest the descent immediately. Also; when we received the GPWS warning; I asked him to climb; but he only decreased his descent rate a little which is contrary to our training. As a company; we are sending him to training with additional mountain training; and will be performing an IOE with him again in an effort to ensure his judgment; flying skills; and attitude fall in line with our company's policies and 'best practices.'
Original NASA ASRS Text
Title: Hawker 800 Check Pilot describes an approach into ASE that results in a missed approach due to not breaking out. On the second approach the Captain under instruction acquires the airport visually at 9 miles and continues descent below applicable stepdown altitudes despite the reporter's instructions to comply with the altitudes. This results in a GPWS warning and a low altitude alert from ATC. A normal landing ensues.
Narrative: The leg was a passenger leg to ASE and the weather initially was overcast 3;500 feet. We initiated the approach; descended to our minimums which are 3;100 feet; but most likely due to the slow rate of descent; we reached the missed approach point without breaking out. I called for the missed approach; which we executed; and we went out to hold. I queried ATC to see if the next aircraft made it in; and if so; what he reported the bases to be; and they said bases were still 3;500 feet. At this point we asked for a second approach; fully configured by DBL; and initiated the approach. The weather had almost completely blown through at this point and we had a visual of the field probably about 9 miles out. The pilot flying asked if he could descend to which I informed him 'a little bit' as we were still a couple of hundred feet above the published minimums for the approach. However; the flying pilot began a rapid descent and I told him to check his descent. He replied by saying he had the runway in sight and didn't want to pop back into the clouds; but I didn't see that there were any clouds above us; and I knew we needed to comply with the approach minimums even though we had a visual of the runway. The flying pilot continued to descend even after I told him to check his descent which resulted in a GPWS warning for terrain. At this same time; the tower called and asked us to immediately check our altitude as they were reporting that we were getting too close to the terrain. I informed the tower that we had a visual on the mountains and the runway; but I was very uncomfortable that the flying pilot decided to descend excessively for some reason. We landed without any further issues. The flying pilot is a fairly new pilot with our company; although he has a good deal of experience in the airplane. One of the reasons I was flying with him that day was to observe how he did flying into a mountainous airport. As the non-flying pilot; I was there to assist him with the approach and make sure everything was set up and executed correctly and on time. I believe I made a mistake when I did not strongly verbalize the minimum altitudes while directing him to arrest the descent immediately. Also; when we received the GPWS warning; I asked him to climb; but he only decreased his descent rate a little which is contrary to our training. As a company; we are sending him to training with additional mountain training; and will be performing an IOE with him again in an effort to ensure his judgment; flying skills; and attitude fall in line with our company's policies and 'best practices.'
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.