EMB-505 / Phenom 300
Flight Crew Air Transport Pilot (ATP)
Communication Breakdown; Time Pressure
Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Unstabilized Approach
Flight Crew FLC complied w / Automation / Advisory; Flight Crew Took Evasive Action
Environment - Non Weather Related; Human Factors
Because the weather was very clear VMC; we selected the visual to [Runway] XX. My partner briefed a 45 entry to the left downwind to XX. His briefing was somewhat truncated due to fatigue. He missed briefing pattern altitude; so I pointed out to him; 2700 MSL or 1500 AGL. We were late in picking up the field because it was hard to see. We were inside 5 miles when we finally saw it. He began maneuvering and descending to pattern altitude while I was busy cancelling IFR; squawking 1200 and communicating on UNICOM. While I was busy; he set 1700 in the altitude alerter mistakenly thinking it was pattern altitude. As we blew through 2700 I noticed how low we were and said I think we are low. As we continued descending; I noticed he leveled at 1700 and told him he needed to climb. He acknowledged; but failed to climb. We ended up flying the pattern at between 500 and 800 AGL. We began configuring; and after flaps 1; we got the gear GPWS warning. On final; he became high and fast; but was able to get somewhat stable by 300 feet. We landed long down the runway; but got it stopped.Fatigue was a huge issue; it clouded our judgment and weakened our briefing and situational awareness. I should have emphasized the points he missed on the briefing. I should have been more forceful in making him climb back to 2700. I should have called for a go around when he was not stable by 500 ft.
The Captain of an EMB-505 reported that they flew the pattern at between 500 and 800 AGL when they got a GPWS warning.