Date: 202102
Local time of day: 0001-0600
Location: OMA.Airport, NE
Flight conditions: VMC
Light: Night
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class C OMA
ATC / advisory: Tower OMA
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Confusion; Situational Awareness; Communication Breakdown
Second reporter function: First Officer; Pilot Flying
Anomaly: Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew FLC complied w / Automation / Advisory; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Human Factors; Procedure; Chart Or Publication
Primary problem: Human Factors

Narrative: Flight was all normal until we were cleared for a visual approach. Approach vectored us about 2 miles outside of the Final Approach Fix. When cleared for the a visual approach the First Officer turned inside of the Final Approach Fix. We had briefed the towers and their height and had them visually. The First Officer turned off the flight directors and turned directly towards the runway; about 20 degrees angle.  At 1;000 feet Tower called and asked if we had the towers in sight and said he had gotten an altitude alert.  At that point we were still visual with the towers and a half dot low on the glide slope. I directed the First Officer to come left and get on final. We continued the approach and landed. Found out afterwards this was the First Officer's first time to this airport and that he really didn't have a good visual on the runway. I felt his turning off the flight directors added to his lack of situational awareness. We discussed this approach afterwards and he felt I should have directed a go around. I believe he was waiting for me but I was in the green.  I didn't know he was lost. I explained to the First Officer that there is a reason we brief instrument approaches at night; to use them.  I shouldn't have allowed him to make the turn directly towards the runway but told him to intercept closer to the Final Approach Fix. The First Officer needed to communicate he wasn't in the green and execute a go around if he felt it was needed.


Second narrative: Cleared visual approach after I stated to the Captain that I had the beacon in sight. I turned toward the airfield and began my descent referencing the glideslope. I only saw the beacon; not the runway. Tower issued a low altitude alert as I flew too close to the towers west of the field. I had the towers in sight and the Captain gave me verbal commands to help me orient the runway. The landing and rollout were uneventful. I accepted a visual approach based on the beacon alone. I was also distracted by the airspeed going below the hook for reasons I didn't understand. After landing; the Captain and I thoroughly debriefed the approach and landing.


Synopsis: A Flight Crew conducting a Visual Approach at night reported the Pilot Flying turned towards the runway prior to the Final Approach Fix and was issued a Low Altitude Alert from the Tower.