Narrative:

I was working a crossing position at lal (lakeland linder regional) at the intersections of runways 5/23 and 9R/27L. An FAA van pulled up. I recognized the driver as a co-worker and asked him if he wanted to cross. He answered in the affirmative. I then asked if he was monitoring the communication (he had a headset on) and said he was. I told him of the departing traffic (a flight of 4 rvs) and instructed him to wait for a gap to cross. As the rvs passed overhead; he proceeded to cross; however; an aircraft had already started its departure roll. When the van exited the runway I estimate the aircraft was already airborne and 500-750 ft from the crossing point. I believed this to be a runway incursion and later asked him if there were any waivers to this. His answer was unacceptable and I told him it was my duty to report this. I do think that this is standard practice at this event. During my initial training when I questioned my team lead about using suitable markers for estimating distance between successive arrivals and departures; I was told not to worry about it; this may be waived. I was unable to determine this from my training material. From my direct observation I felt the distance requirements were basically ignored; in addition the rule that the preceding aircraft has landed or airborne requirement also ignored. While training on departure position lal; a flight of 2 A10 warthog jets on low approach runway 27L; immediately after passing the intersection my instructor told me to clear several small aircraft for takeoff. I questioned the wake turbulence separation and was instructed to give them a cautionary advisory and clear them. I felt this may not meet the requirement but was unable to verify that.

Related reports:

Google
 

Original NASA ASRS Text

Title: LAL Controller described several operational events; questioning facility practiced standards vs. published FAA requirements.

Narrative: I was working a crossing position at LAL (Lakeland Linder Regional) at the intersections of Runways 5/23 and 9R/27L. An FAA van pulled up. I recognized the driver as a co-worker and asked him if he wanted to cross. He answered in the affirmative. I then asked if he was monitoring the communication (he had a headset on) and said he was. I told him of the departing traffic (a flight of 4 RVs) and instructed him to wait for a gap to cross. As the RVs passed overhead; he proceeded to cross; however; an aircraft had already started its departure roll. When the van exited the runway I estimate the aircraft was already airborne and 500-750 FT from the crossing point. I believed this to be a runway incursion and later asked him if there were any waivers to this. His answer was unacceptable and I told him it was my duty to report this. I do think that this is standard practice at this event. During my initial training when I questioned my Team Lead about using suitable markers for estimating distance between successive arrivals and departures; I was told not to worry about it; this may be waived. I was unable to determine this from my training material. From my direct observation I felt the distance requirements were basically ignored; in addition the rule that the preceding aircraft has landed or airborne requirement also ignored. While training on departure position LAL; a flight of 2 A10 Warthog jets on low approach Runway 27L; immediately after passing the intersection my Instructor told me to clear several small aircraft for takeoff. I questioned the wake turbulence separation and was instructed to give them a cautionary advisory and clear them. I felt this may not meet the requirement but was unable to verify that.

Data retrieved from NASA's ASRS site as of April 2012 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.