 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Air carrier SF34 flight crew, cleared to land behind dash 7, initiates a go around due to aircraft on runway. At time of go around, tower has cleared a B737 for departure from a crossing runway. The SF34 PIC observes the B737 climbing in conflict with his aircraft and initiates an evasive turn. Neither the tower nor the B737 apparently see what has taken place. First officer states if it were not for PIC taking evasive action, a collision seemed obvious.
| Attributes | |
| ACN | 413363 |
| Time | |
| Date | 199809 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : mia |
| State Reference | FL |
| Altitude | msl bound lower : 500 msl bound upper : 500 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tower : mia |
| Operator | common carrier : air carrier |
| Make Model Name | SF 340B |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | cruise other landing : go around |
| Route In Use | approach : visual arrival other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737 Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | climbout : initial |
| Route In Use | departure other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : cfi pilot : atp |
| Experience | controller radar : 5 flight time last 90 days : 250 flight time total : 2150 flight time type : 300 |
| ASRS Report | 413636 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | conflict : nmac non adherence : required legal separation other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : took evasive action |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Operational Error |
Narrative:
Simultaneous operations on runways 9R&left and runway 12 were in operation. We were on vectors when cleared for the visual runway 9R, reference to our traffic, a dash 7, and hold short of runway 12. We were then asked to slow to final approach speed for spacing. I immediately configured and slowed to final approach speed. The dash 7 landed and took its time on rollout and taxiing clear. I do not recall any communication to the dash 7 pertaining to expeditious clearing or suggesting an intersection. At some time during this approach, the tower launched a B737 from runway 12. We were on GS and approximately over the displaced threshold when we decided to go around. While climbing straight ahead and configuring the airplane, the captain saw the B737 converging out of his left side window. I did not hear any reference made to its position from the tower, nor did I hear any reference made of us to him. The captain immediately grabbed the yoke and applied full right aileron until we were in approximately a 60 degree bank. When we were clear of the conflict, we were vectored around and landed on runway 9R. With the captain's estimate of the distance of the converging B737 and its apparent nonevasive turn, and absolutely no help from the tower, there would have been disaster.
Original NASA ASRS Text
Title: ACR SF34 FLC, CLRED TO LAND BEHIND DASH 7, INITIATES A GAR DUE TO ACFT ON RWY. AT TIME OF GAR, TWR HAS CLRED A B737 FOR DEP FROM A XING RWY. THE SF34 PIC OBSERVES THE B737 CLBING IN CONFLICT WITH HIS ACFT AND INITIATES AN EVASIVE TURN. NEITHER THE TWR NOR THE B737 APPARENTLY SEE WHAT HAS TAKEN PLACE. FO STATES IF IT WERE NOT FOR PIC TAKING EVASIVE ACTION, A COLLISION SEEMED OBVIOUS.
Narrative: SIMULTANEOUS OPS ON RWYS 9R&L AND RWY 12 WERE IN OP. WE WERE ON VECTORS WHEN CLRED FOR THE VISUAL RWY 9R, REF TO OUR TFC, A DASH 7, AND HOLD SHORT OF RWY 12. WE WERE THEN ASKED TO SLOW TO FINAL APCH SPD FOR SPACING. I IMMEDIATELY CONFIGURED AND SLOWED TO FINAL APCH SPD. THE DASH 7 LANDED AND TOOK ITS TIME ON ROLLOUT AND TAXIING CLR. I DO NOT RECALL ANY COM TO THE DASH 7 PERTAINING TO EXPEDITIOUS CLRING OR SUGGESTING AN INTXN. AT SOME TIME DURING THIS APCH, THE TWR LAUNCHED A B737 FROM RWY 12. WE WERE ON GS AND APPROX OVER THE DISPLACED THRESHOLD WHEN WE DECIDED TO GAR. WHILE CLBING STRAIGHT AHEAD AND CONFIGURING THE AIRPLANE, THE CAPT SAW THE B737 CONVERGING OUT OF HIS L SIDE WINDOW. I DID NOT HEAR ANY REF MADE TO ITS POS FROM THE TWR, NOR DID I HEAR ANY REF MADE OF US TO HIM. THE CAPT IMMEDIATELY GRABBED THE YOKE AND APPLIED FULL R AILERON UNTIL WE WERE IN APPROX A 60 DEG BANK. WHEN WE WERE CLR OF THE CONFLICT, WE WERE VECTORED AROUND AND LANDED ON RWY 9R. WITH THE CAPT'S ESTIMATE OF THE DISTANCE OF THE CONVERGING B737 AND ITS APPARENT NONEVASIVE TURN, AND ABSOLUTELY NO HELP FROM THE TWR, THERE WOULD HAVE BEEN DISASTER.
Data retrieved from NASA's ASRS site as of July 2007 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.