Date: 201408
Location: BFI.Airport, WA
Flight conditions: VMC
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class D BFI
ATC / advisory: Tower BFI
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Human factors: Human-Machine Interface; Situational Awareness; Communication Breakdown; Confusion
Anomaly: Deviation - Altitude Excursion From Assigned Altitude; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy; Flight Deck / Cabin / Aircraft Event Other / Unknown
Detector: Person Flight Crew; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were on a ferry flight to BFI which is literally 5 miles away from SEA and during the flight there were numerous SOP's that were not followed by the Captain. We had been vectored downwind to BFI when ATC asked if we had it in sight. The Captain said that he had it in sight and we were cleared for the visual to Runway 31; maintain 2;000 feet until turning final. The Captain immediately turned his base leg and began a descent with the speed brakes and all auto[pilot] off. I was concerned about this as we had plenty of distance from the airport and I hadn't even started any of the checklists.I was completing the approach descent checklist when I noticed the VSI at around -2200 FPM and that the flaps had been placed to position 1. I hadn't moved the flaps nor was I asked to. These kind of non-standard procedures get the non flying pilot completely out of the loop as I was 'heads down' loading approaches; destination data and activating the approach all while doing the checklists. I was also concerned about his altitude going below 2;000 feet before tuning final but when I looked up he was lined up for a runway. At that time I was crosschecking with the ILS that I had programmed into the box and it didn't line up. As I was analyzing this in my head it began to become clear to me that this was in fact the wrong airport and quickly heard ATC tell us that we were lined up for Renton and to go around.In retrospect; I should have addressed the non-SOP's a couple of years ago when I first flew with this Captain. I was already a little nervous and on guard before I even showed up at the airport so my lack of communicating concern didn't help this situation. I am an SOP pilot and the breakdown of that as well as communication in the cockpit contributed to this problem. I have never landed at BFI or Renton but was vaguely familiar with both. This I feel contributed to my not immediately recognizing that we were in fact lined up for the wrong airport. In summary; I strongly feel that if this flight had been conducted in a purely SOP environment that this problem would have never occurred.As stated before; I have been consulting with colleagues as to what I should do about this situation and was so focused on the professional standards aspect of it that I simply forgot to file the flight safety report in a timely manner.




Synopsis: Air carrier First Officer reported they lined up to land at RNT instead of their intended BFI destination.  The flight crew executed a go-around after ATC pointed out the error.  Reporter stated non-compliance with SOPs contributed to the event.