CRJ-700 flight crew reported receiving an obstacle alert during a night visual approach. After responding accordingly to the alert; the flight crew followed the company approach guidance to a safe landing.

2022-10 · NASA ASRS report 1942817

Date: 2022-10 · Aircraft: Regional Jet 700 ER/LR (CRJ700)

Anomalies: deviation-altitude-excursion-from-assigned-altitude|deviation-altitude-overshoot|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-far|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-cftt-cfit|inflight-event-encounter-weather-turbulence

Synopsis

CRJ-700 flight crew reported receiving an obstacle alert during a night visual approach. After responding accordingly to the alert; the flight crew followed the company approach guidance to a safe landing.

Narrative

After two unsuccessful attempts to land at ZZZ1 Airport due to weather. We diverted to ZZZ where we setup for a visual approach to Runway X. We used the RNAV (GPS) Y Runway X approach to back up the visual approach as the ILS approach was out of service. On right downwind for Runway X ATC asked if we had the airport in sight which we did. They cleared us for the visual approach and we continued downwind. We turned about a 5 mile base leg and were descending to 6100. We received an obstacle alert and responded accordingly. This is when I realized that we were improperly conducting a visual approach into ZZZ. I had forgot that we needed to follow the approach guidance from an IAF or radar vectors for this airport. Both of us missed that point during the approach briefing. After adjusting our descent rate for the alert we continued the approach without further incident. After conducting two missed approaches from minimums and diverting with considerable weather in the area that we were constantly avoiding we were mentally fatigued and overlooked the safety alert airport requirements for approaches into ZZZ at night. I am familiar with this airport and its requirements as I have been here many times before. I think the contributing factors involved in our error were rushing during a diversion at night and task saturation that caused us to overlook the requirement. Also contributing was the late hour at the end of a long day and get-there-itis.

Second reporter narrative

We departed the airport and knew we'd be dealing with weather both most of the way enroute; and at the destination; at night. After attempting an approach twice with hopes the clouds at minimums were transient; we diverted to our alternate. Enroute; while dodging storms at night; it became clear that there was a better alternate behind us; closer. We again coordinated with ATC to turn towards that airport. Due to its proximity and the nature of the irregular ops; we were somewhat task saturated for a bit. We felt good about our decision and focused on the flight path management in relation to the weather; as well as all the briefings; etc. During the approach to landing; cleared for a visual approach and in good VMC; I turned the plane to a base leg; and rolled the VS knob down because we had been high. While communicating with the Captain about my decision to turn now; and configuring; our flight path became low in relation to our vertical guidance. It was VMC and we had a clear view to the airport and runway. I was either slowing my descent or had leveled when an obstacle alert sounded. I clicked off AP; applied thrust and started a climb. The alert went away immediately; and the vertical guidance was realigned on the 3 degree glideslope soon after. We continued the approach and landed uneventfully; and during the debrief the Captain informed me of our mistake. Weather both enroute and at the original destination airport. Multiple missed approaches both ending in a hold. Intermittent icing; especially during high work load times. The entire flight was at night. Flying well in to the night.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.

Which aircraft types can I filter by?

We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.

Is FlightFinder free to use?

Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.

Where does the route data come from?

Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.