Only in circumstances where things are going to plan. In which case - why are you making the players make checks anyway?
The thing is, 'oh [expletive]' moments are the point at which you should be making the players take skill checks - so whilst DEX checks for piloting may only represent 0.1% of pilot manouvres, they will represent a good >50% of the times the GM should actually be making you roll dice.
For example:
Landing at a starport is a Routine (+2) task for most ships taking 10–60 seconds.
Does
NOT mean that starships flown by someone with pilot/0 crash every one in three landings they attempt. That would be blatantly ridiculous. But that's the base difficulty to use when something else is making the landing difficult or dangerous (like a storm, or unresponsive controls, or a really, really angry aslan with a particle beam turret).
Agree with GypsyComet. You can use whatever you'd prefer. I tend to vary it based on circumstances.
INT is for "I chart a course, punch it into the computer and press go" where you're planning out a route.
DEX is for "holy crud holy crud the ship in the docking pattern ahead of us just exploded" where exactly what course you're changing
to is less important than
not being on the one you're
currently on in a second's time.
EDU plus pilot might be used for figuring out the safe route in the first place.
Hell, END plus pilot might be used for keeping control of the ship under appropriately extreme circumstances (i.e. can you stay concious enough to land the ship).
There is virtually no skill that will only ever use a single stat.
Taking TFR* aircraft flight as an example, yes you'd fly a fighter at low level by computer for waypoint-to-waypoint transit but you'd go to manual once you reach a perceived threat zone. Once a hazard warning starts bleeping, the manouvres you're doing are most definintely DEX/END type checks, not INT.
*Terrain Following Radar