Runway incursion and FSDO aftermath

[MAKG1]

in order for the FSDO to get notified in a situation like there there must have been a loss of separation - good thing that was all.

No, it seems the tower guys at KRHV have flagpoles stuck up their butts. Well, more precisely, they are trainees with inadequate supervision.

See my post on my "possible PD." It happened there, too. I got cleared because the instruction really was AFU. I did what I was told and got written up anyway.

My "error" was supposedly taxiing without a clearance, not a runway crossing. But what really happened was the tower controller cleared me when he didn't mean to. The "possible PD" was resolved as remedial instruction for the controller.

 

[Marauder]

 

[RotorAndWing]

in order for the FSDO to get notified in a situation like there there must have been a loss of separation

Nope.

 

[comanchepilot]

Nope.

Not legally - practically. . . . or you caused a go around, or a canceled T/O clearance - something happened to cause the on duty controller and supe to report it . . .

 

[Norman]

What I would like to know is how they got approval for paralell runways with only 225 feet between them.

 

[Matthew]

What I would like to know is how they got approval for paralell runways with only 225 feet between them.

I guess they didn't plan on landing an A380 there.

 

[Everskyward]

The reason that KFCM (Flying Cloud) came to mind is that we were there recently and told to hold short between the runways. We told them that we were holding short but suspected our tail was hanging over the line behind us. (Airplane is 64' long).

 

[Ted]

The reason that KFCM (Flying Cloud) came to mind is that we were there recently and told to hold short between the runways. We told them that we were holding short but suspected our tail was hanging over the line behind us. (Airplane is 64' long).

 

[kkoran]

According to Google Maps, the distance between the hold lines is 45 ft.