Commercial Fixed Wing
Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Situational Awareness; Workload; Communication Breakdown; Distraction
Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Ground Event / Encounter Other / Unknown; Inflight Event / Encounter CFTT / CFIT; No Specific Anomaly Occurred Unwanted Situation
Flight Crew Overrode Automation
Software and Automation; Environment - Non Weather Related
We were flying into GUC in a non RNP aircraft. Winds were 250/11; SKC; elected to fly [Runway] 06 approach per ops pages; then enter downwind via Plato to GU24D. Used RNAV for SA (Situational Awareness); but did not Nav due to UNABLE RNAV RNP. When level at 9200 feet in valley on down wind; received 3 separate GPWS 'terrain; terrain' erroneous indications. There was no terrain and we were not descending. Additionally; there was no red GPWS indications on ND; just the aural cue one time with red warning light. I was the PF (Pilot Flying); and we both were perplexed by the indication. We continued the approach; as there was no reason to react to this partial warning. This event did make us question our flight path; but we also agreed that all was performed correctly. We didn't see any warnings about erroneous GPWS; and the Aircraft appeared to have no issues. We both also agreed that flying a Basic airplane that is not RNP capable into Gunnison was unsatisfactory. Are we to land with a 10 kt. tailwind to avoid indications such as this when performing the pattern as prescribed by the company?Flying a Basic; non-RNP AC into a challenging mountainous terrain airportOur original aircraft was swapped out for some reason. Non RNP airplanes should go to basic destinations.
Air Carrier Pilot reported 3 false terrain warnings on approach in a non-RNP aircraft.