Date: 201808
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class D ZZZ
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Not Flying
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Workload
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning; Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: While flying the [approach; the] aircraft descended to approximately 800 AGL during visual approach prior to the final segment. Following descent clearance and subsequent clearance to fly the [approach]; and on the offshore segment of the approach; tower instructed us to 'square off' the turn to final for traffic in the pattern. Additional traffic was called to our 3 o'clock position. At this time I confirmed the instructions to the CA (Captain) (Pilot Flying) and immediately began a visual scan for the traffic. I glanced back to the PFD and called 'You're at 1;250 feet;' to call attention to the CA that we were getting low for our distance from the airport. I went back outside the aircraft momentarily to scan for the called traffic. Next time I looked inside we were at 800 feet AGL. I immediately called the deviation to the CA; saying; 'check altitude - 800 feet.' As the CA corrected immediately tower called; 'Low altitude alert; 700 feet.' The CA regained altitude to approximately 1;200 AGL prior to commencing final descent to the airport. The flight continued without further incident. The CA had disconnected the AP during the initial descent phase of the visual approach. During the descent; the CA was sequencing waypoints manually on the FMS; including programming and cleaning up the approach. Throughout the flying day; the CA was very hands on and performing several PM (Pilot Monitoring) tasks while he was PF (Pilot Flying). I feel that should SOPs regarding PF/PM duties had been adhered to during the flight the likelihood of the incident occurring would have been significantly reduced. I also feel that disconnecting the autopilot and hand-flying the approach would not have been a bad thing in itself should PF/PM duties had been followed. The CA hand-flying a visual approach while being heads-down into the FMS contributed to the lack of attention to altitude. The adjustment of the approach per ATC instructions was a contributing factor. The additional traffic called by tower (but not depicted on TCAS) at our 3 o'clock (which was in the direction of our turn back to the airport) took my attention as PM from monitoring flight data to an outside visual scan for traffic.Reinforcement of CRM during critical phases of flight. Reinforcement that hand-flying the aircraft requires complete attention to flight instruments by the PF.




Synopsis: CRJ First Officer reported the Captain descended early on a visual approach and failed to follow SOP's on several occasions.