F11 controller described an unsafe condition involving sfr departure procedures noting the addition ...

Narrative:

King air departed off runway 27R and a BE33 departed runway 27C on diversion headings; problem is both aircraft on 2 different departure frequencies; on 2 different satellite's radar scopes; with runways less than 1;000 ft apart and the departure corridor for runway 27C are in satellite's north airspace. Due to bad procedures in order for sanford to move traffic and a poor letter of agreement with sanford tower to move traffic; a safety issue has shown to prove this is a bad operation. Sanford airport procedures were designed for a 1 runway operation. Now they have 3 departing runways with 2 different local positions to 2 different departures scopes; with a huge amount of traffic; this letter and old procedures are no longer safe and needs to be addressed. This has been a known problem with sanford airport and no one wants to address these procedures and now this has become a safety issue! There has been numerous close calls due to these procedures and the way sanford tower interprets there version of the LOA that they can depart southeast bound traffic off the north runway and northeast bound traffic of the south runway at the same time and then on two different frequencies and not be liable or provide a service to the pilot; in the mean time put added pressure on the F11 controllers to be responsible to keep separation and put the aircraft on course. Being that sanford airport is a class C airspace; there needs to be some kind of procedure for the tower to taxi for direction or provide a safe environment for aircraft they launch into satellite airspace. Hopefully this will cause an investigation for a new and simpler LOA (and not a 10 page letter) with new procedures for a safe operation here at a very busy little airport; with smarter or more informed controllers. Bad and old procedures here at sanford just rose its head and hopefully someone will finally have the guts to take care of this!

Original NASA ASRS Text

Title: F11 Controller described an unsafe condition involving SFR departure procedures noting the addition of a Local Control position coupled with more runway procedures require the need of new LOA revisions.

Narrative: King Air departed off Runway 27R and a BE33 departed Runway 27C on diversion headings; problem is both aircraft on 2 different departure frequencies; on 2 different satellite's RADAR scopes; with runways less than 1;000 FT apart and the departure corridor for Runway 27C are in satellite's north airspace. Due to bad procedures in order for Sanford to move traffic and a poor Letter of Agreement with Sanford Tower to move traffic; a safety issue has shown to prove this is a bad operation. Sanford Airport procedures were designed for a 1 runway operation. Now they have 3 departing runways with 2 different Local positions to 2 different departures scopes; with a huge amount of traffic; this letter and old procedures are no longer safe and needs to be addressed. This has been a known problem with Sanford Airport and no one wants to address these procedures and now this has become a safety issue! There has been numerous close calls due to these procedures and the way Sanford Tower interprets there version of the LOA that they can depart southeast bound traffic off the north runway and northeast bound traffic of the south runway at the same time and then on two different frequencies and not be liable or provide a service to the pilot; in the mean time put added pressure on the F11 Controllers to be responsible to keep separation and put the aircraft on course. Being that Sanford Airport is a Class C airspace; there needs to be some kind of procedure for the Tower to taxi for direction or provide a safe environment for aircraft they launch into satellite airspace. Hopefully this will cause an investigation for a new and simpler LOA (and not a 10 page letter) with new procedures for a safe operation here at a very busy little airport; with smarter or more informed controllers. Bad and old procedures here at Sanford just rose its head and hopefully someone will finally have the guts to take care of this!

Data retrieved from NASA's ASRS site as of July 2013 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.

Attributes
ACN	1073400
Time
Date	201303
Local Time Of Day	1201-1800
Place
Locale Reference	SFB.Airport
State Reference	FL
Aircraft 1
Make Model Name	Bonanza 33
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	King Air C90 E90
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Deviation - Procedural Other / Unknown

F11 controller described an unsafe condition involving sfr departure procedures noting the addition of a local control position coupled with more runway procedures require the need of new LOA revisions.