EMB-175 pilot reported low fuel resulted in a diversion to an unfamiliar airport. Upon arriving at approach minimums the flight crew mistook a pond for the runway and flew toward it briefly before correcting back on course and landing.

Date: 2023-11 · Aircraft: EMB ERJ 170/175 ER/LR

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-clearance|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-fuel-issue|inflight-event-encounter-cftt-cfit|inflight-event-encounter-weather-turbulence

Synopsis

EMB-175 pilot reported low fuel resulted in a diversion to an unfamiliar airport. Upon arriving at approach minimums the flight crew mistook a pond for the runway and flew toward it briefly before correcting back on course and landing.

Narrative

I served as the PF for flight XXXX from ZZZ to ZZZ1; this is the outline of the factors that contributed to our unscheduled diversion to ZZZ2.Initially; our released fuel was set at 20.5 lbs; but due to constraints with the fueler being unable to physically complete the fuel order; as the aircraft could no longer accept any more fuel; we had to settle for 20.1 lbs. We discussed the fuel issue but since we were above the minimum fuel requirement of 19.8 lbs; we accepted the release.Upon reaching our initial cruise altitude of FL340; we encountered strong headwinds; causing our planned arrival fuel to decrease from 4800 lbs to 3200 lbs. In an effort to mitigate this; we descended to FL300; where the headwinds were reported to be weaker; increasing our arrival fuel to 4200 lbs. However; the turbulent conditions at this altitude prompted us to return to FL320.Throughout the flight; we monitored updates on the weather at ZZZ1; ensuring it remained within our operational limits. As we approached; ATC rerouted us south; resulting in a lengthy right downwind for RWY XX and further impacting our arrival fuel.While executing the LNAV approach; heavy rain at ZZZZZ forced a go-around upon reaching ZZZZZ1 (MAP). In response to the unexpected deterioration; the captain [requested priority with ATC] with approximately 2700 lbs of fuel. ATC provided alternate options; and we chose ZZZ2; which was 20 nm away; over ZZZ3 due to its proximity.During the approach into ZZZ2; we encountered challenges as we lacked airport information and plates on our iPads. The approach building and execution was done in a very small amount of time with a very small amount of information; causing a highly task-saturated situation. Despite this; the FMS data for the approach was onboard the aircraft and with guidance from ATC; we successfully executed the RNAV approach. However; a minor confusion arose in searching for the RWY during the approach due to the possibility of the baro mins not adjusted correctly or the app mode was not selected; causing the aircraft to announce 'MINIMUMS' at a higher altitude than the DA/DH.While I was at the controls during the approach; MINIMUMS" was announced and we searched for the RWY but could not identify one. The Captain identified what appeared to be a rectangular-shaped pond; briefly mistaking it for a runway; took control; and flew in that direction for a short period of time. After communicating this was not the runway; prompt correction was made. We realigned our course with guidance from TWR and safely completed the landing. We landed with approximately 2100 lbs of fuel.We spent the next two hours at ZZZ2 due to the lack of airport information and the absence of appropriate service utilities for passenger disembarkation. After obtaining performance calculations from the engineer; we safely departed ZZZ2 and arrived at ZZZ without further issues.The incident was a challenging experience; and we acknowledge the need for improvement in our approach to unexpected diversions and the importance of ensuring comprehensive airport information is readily available.Cause: Unexpected weather conditions caused us to use more fuel than anticipated; causing us to enter into a min fuel situation. Suggestions: Anticipate going around and fueling up at an intermittent location."

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