 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A B737-800 pilot reports being instructed to maintain 180 KTS to the FAF for runway 9 by ATC and advising unable. Upon landing ATC instructs the crew to turn off at H4 then H5 (no longer exist) then cancels the takeoff clearance of an aircraft departing on runway 12. The B737 crew is admonished by ATC for not advising that they will be using the whole runway.
| Attributes | |
| ACN | 1038834 |
| Time | |
| Date | 201209 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | MIA.Airport |
| State Reference | FL |
| Environment | |
| Flight Conditions | IMC |
| Aircraft 1 | |
| Make Model Name | B737-800 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Landing |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
We were on final to runway 9 in mia; in IFR conditions. My company requires us to be in the landing configuration by the final approach fix. Tower asked us to maintain 180 KTS to the marker; we declined and offered 160 KTS so that we could be configured; yet allow us to be stabilized by 1;000 ft. ATC not pleased. On landing rollout; with a slight tailwind; wet runway and 3/4 visibility and decelerating through 85 KTS tower tells us to take H4 taxiway; then H5 taxiway. We did not answer until we were slowed to taxi speed. During this same time tower cleared another carrier to takeoff on runway 12 which intersects runway 9; our landing runway. We were able to stop short of runway 12; and then tower canceled the takeoff clearance for the other plane. We were never given any land and hold short instructions; which we would have declined; before landing. Tower said that if we wanted to use the whole runway then we need to tell them before hand. My understanding is that the runway is mine until clearing to taxi and don't have to tell them that information. We cleared and taxied to the gate. This was a potentially dangerous situation because of tower's noncompliance with regulations.
Original NASA ASRS Text
Title: A B737-800 pilot reports being instructed to maintain 180 KTS to the FAF for Runway 9 by ATC and advising unable. Upon landing ATC instructs the crew to turn off at H4 then H5 (no longer exist) then cancels the takeoff clearance of an aircraft departing on Runway 12. The B737 crew is admonished by ATC for not advising that they will be using the whole runway.
Narrative: We were on final to Runway 9 in MIA; in IFR conditions. My company requires us to be in the landing configuration by the final approach fix. Tower asked us to maintain 180 KTS to the marker; we declined and offered 160 KTS so that we could be configured; yet allow us to be stabilized by 1;000 FT. ATC not pleased. On landing rollout; with a slight tailwind; wet runway and 3/4 visibility and decelerating through 85 KTS Tower tells us to take H4 Taxiway; then H5 Taxiway. We did not answer until we were slowed to taxi speed. During this same time Tower cleared another carrier to takeoff on Runway 12 which intersects Runway 9; our landing runway. We were able to stop short of Runway 12; and then Tower canceled the takeoff clearance for the other plane. We were never given any land and hold short instructions; which we would have declined; before landing. Tower said that if we wanted to use the whole runway then we need to tell them before hand. My understanding is that the runway is mine until clearing to taxi and don't have to tell them that information. We cleared and taxied to the gate. This was a potentially dangerous situation because of Tower's noncompliance with regulations.
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.