B737-300
Flight Crew Last 90 Days 208; Flight Crew Type 12000
Workload; Distraction; Training / Qualification; Communication Breakdown
ATC Issue All Types; Aircraft Equipment Problem Critical
Flight Crew FLC complied w / Automation / Advisory; Flight Crew Overcame Equipment Problem; General Declared Emergency
Aircraft; Airport
After declaring an emergency for a split flap condition; we diverted and executed a Flap less than 1; LED full landing IAW our QRH. Landing was uneventful; and we had informed Tower that we would like to stop straight ahead on the runway and let emergency equipment take a look at the aircraft for blown tires; damage; etc. We brought the aircraft to a stop on runway and were told to switch to Ground frequency; which we did. We were not able to communicate with emergency vehicles effectively because Ground Control was giving a continuous stream of taxi directions to a multitude of aircraft. Other than occasional one or two word exchanges; we had no contact with fire trucks at all; and did not know their position. We finally switched back to Tower and asked if there was a discrete frequency we could use to coordinate with fire/rescue. Tower said that there was not; but to go back to Ground. After about 10 minutes we finally learned that our aircraft was OK to continue to the gate; which we did. In talking with the fire/rescue operators afterward; they acknowledged frustration with not having a dedicated frequency and having to work around Ground Control. The airport really needs to have a more effective means of communicating between emergency aircraft and fire/rescue. The situation we encountered was unacceptable.
A B737-300's trailing edge flaps did not extend on approach; but the leading edge devices did. An emergency was declared; the QRH completed and a successful landing completed but the crew had communications difficulty with Air Crash Fire crews.