37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1225695 |
Time | |
Date | 201412 |
Local Time Of Day | 1201-1800 |
Environment | |
Flight Conditions | IMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Global 5000 (Bombardier) |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Vectors STAR ADGE1F |
Flight Plan | IFR |
Person 1 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 40 Flight Crew Total 4800 Flight Crew Type 1300 |
Events | |
Anomaly | Inflight Event / Encounter CFTT / CFIT |
Narrative:
Aircraft was routing via the ADGE1F for the ILS 34 [at ubbq]. From adgen the aircraft was descended to FL060 by ATC. From position lusal the aircraft was given a radar vector in a northwest direction and cleared to descend to 3000ft on qnh 1028 by ATC. Aircraft was fully configured for landing at GS intercept and established on the localizer. Shortly after descent on the glideslope (GS) the egpws system initiated a GPWS caution message. 5 seconds later a gwps warning was sounded. The pilot flying initiated an immediate missed app following the published missed app routing and climbing to 3800ft under ATC instruction. Aircraft was routed via radar vectors maintaining 3800ft for the ILS RWY34 and landed safely.both crew members were unfamiliar with the airport and have never flown there before. The flight was conducted in IMC with icing conditions and the aircraft was under radar control. The aircraft was established after the FAF within 5 nm from the runway with localizer and GS green.the only option the crew had was to respond to the egpws warning despite the aircraft position at the time. We were unfamiliar with the airport and terrain surrounding it. Spending valuable time to figure out the reason for the warning was not an option.I wish to also mention. On departure RWY34 later that afternoon shortly after rotation prior to raising the gear the GPWS warning sounded again. At this time the aircraft was VMC with no visual reference to impeding terrain. The takeoff was continued.
Original NASA ASRS Text
Title: BD700 Captain reported getting a GPWS terrain warning on approach to UBBQ. The reporter questioned the accuracy of the warning since he got another warning on departure when no terrain conflict was visually apparent.
Narrative: Aircraft was routing via the ADGE1F for the ILS 34 [at UBBQ]. From ADGEN the aircraft was descended to FL060 by ATC. From position LUSAL the aircraft was given a radar vector in a NW direction and cleared to descend to 3000ft on QNH 1028 by ATC. Aircraft was fully configured for landing at GS intercept and established on the LOC. Shortly after descent on the glideslope (GS) the EGPWS system initiated a GPWS caution message. 5 seconds later a GWPS warning was sounded. The pilot flying initiated an immediate missed app following the published missed app routing and climbing to 3800ft under ATC instruction. Aircraft was routed via radar vectors maintaining 3800ft for the ILS RWY34 and landed safely.Both crew members were unfamiliar with the airport and have never flown there before. The flight was conducted in IMC with icing conditions and the aircraft was under radar control. The aircraft was established after the FAF within 5 nm from the RWY with LOC and GS green.The only option the crew had was to respond to the EGPWS warning despite the aircraft position at the time. We were unfamiliar with the airport and terrain surrounding it. Spending valuable time to figure out the reason for the warning was not an option.I wish to also mention. On departure RWY34 later that afternoon shortly after rotation prior to raising the gear the GPWS warning sounded again. At this time the aircraft was VMC with no visual reference to impeding terrain. The takeoff was continued.
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.