Date: 201902
Local time of day: 1201-1800
Location: FCM.Airport, MN
Flight conditions: VMC
Weather elements / visibility: clear; 10
Aircraft: Small Transport
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground FCM
Second aircraft: Skyhawk 172/Cutlass 172
Reporter organization: Corporate
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Second reporter function: Ground
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control
When detected: Taxi
Result: Air Traffic Control Provided Assistance; Air Traffic Control Issued Advisory / Alert; Flight Crew Became Reoriented
Contributing factors: Airport; Human Factors; Weather
Primary problem: Human Factors

Narrative: While taxing out from FBO; I was told to taxi Runway 28L. Because the taxiway [had] piled up snow and the fact that the taxiway extended from the ramp; I missed the taxiway and turned on Runway 28R. The Ground Controller called and told the Pilot Not Flying that we were on the runway; we exited the runway and taxied to Runway 28L and completed the flight.


Second narrative: Aircraft X (BE20) called for taxi from FBO. Aircraft that are assigned Runway 28L for departure on the north side of the airport are instructed to hold short of Taxiway Charlie ON ALPHA; and at that point call Tower; and Tower is responsible to cross them over Runway 28R at Charlie; and depart them off of Runway 28L. The pilot of Aircraft X read back the instructions correctly but seemed a little unsure of himself. A short while; after he called back and asked; 'Was that a left or right turn off the ramp?' I reiterated the same taxi instructions; emphasizing the left turn off the ramp. After that; I took the flight progress strip and the magnetic chip and moved it over to the Local Control podium for the Controller. After I turned back around to observe the aircraft's movement; using binoculars to better see; I observed that Aircraft X had gone straight off the ramp onto taxiway Alpha 3; and made a left turn onto Runway 28R instead of Taxiway alpha. Aircraft Y (a Cessna in the pattern) had already departed Runway 28R pavement; and was climbing out; well above Aircraft X. When Local Control asked [if] Aircraft Y observed a King Air on the runway; they replied that they did not.Our Tower is located so far back from this location on the airfield it is almost impossible to tell with the naked eye whether aircraft are on Runway 28R or Taxiway Alpha. Being that it is also winter; it makes it 10 times more difficult. Tower controllers cannot even see Taxiway Alpha's pavement because of snow drifts blocking the view.As with every runway incursion; wrong runway landing; or safety event that occurs at FCM; I would recommend a NEW HIGHER AND CLOSER TOWER TO THE OPERATION. I know that's a far stretch; but would REALLY solve a lot of our problems at this airport. This facility's location on the airport only impedes the Agency's safety culture and goals. The physical location of the building makes it difficult for us to do our jobs. On busy days when Runway 28L/28R or [Runway]10L/10R parallel operations are in progress; we have a hard time deciphering what runway aircraft are lined up for; all the while trying to keep VFR pilots from running into each other.This problem could have been more quickly and easily noticed if we had a higher building and were closer to the operation.


Synopsis: Part 91 flight crew and ATC reported a runway incursion at FCM airport.