 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Flight crew on B737-300 departing lga runway 31 given expedite takeoff, after previous 2 aircraft had takeoff canceled. On becoming airborne at the far end, the crew saw a dash-8 at approximately 100 ft landing on runway 22. PIC concerned and questions whether standard separation existed.
| Attributes | |
| ACN | 413075 |
| Time | |
| Date | 199809 |
| Day | Sat |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : lga |
| State Reference | NY |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | common carrier : air carrier |
| Make Model Name | B737-300 |
| Operating Under FAR Part | Part 121 |
| Navigation In Use | Other |
| Flight Phase | climbout : takeoff |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Dash 8 Series Undifferentiated or Other Model |
| Operating Under FAR Part | Part 121 |
| Flight Phase | landing other |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Experience | flight time last 90 days : 200 flight time total : 20000 flight time type : 4000 |
| ASRS Report | 413075 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : first officer |
| Qualification | pilot : instrument pilot : commercial |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other controllera other flight crewa |
| Resolutory Action | other |
| Consequence | Other |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | other |
Narrative:
3 airplanes in a row for departure, air carrier Z, air carrier a and air carrier X (my airplane) departing lga runway 31. Air carrier Z was given takeoff clearance, started rolling and had takeoff clearance canceled due to conflict with landing traffic landing runway 22. Air carrier a was then given takeoff clearance only to have it canceled for reasons unknown. Air carrier X was then given clearance. We were already spooled, released brakes immediately and the controller told us words to the effect 'expedite takeoff.' as we cleared the runway 31/22 intersection we saw a dash 8, air carrier Y, at approximately 100 ft on final for runway 22. While it was not a near miss, it was less than comfortable. I question if standard separation was maintained as we were given takeoff clearance even before the previous landing traffic had cleared the runway 31/22 intersection. In view of the 2 previous moderate speed 'takeoff clearance canceled' events I have been involved in and the aircraft/aircraft very near miss, lga tower continues to do business in their very cavalier, 'no problems here' usual method of doing business. Callback conversation with reporter revealed the following information: reporter stated that the dash-8 landing on runway 22 was still over the water when his flight crossed runway 22 on runway 31. He believes controllers at lga are cavalier in their handling of traffic and at times are running aircraft too tight at the intxns. Also said controller used some phrase he had not heard before to indicate he wanted to the crew to expedite takeoff.
Original NASA ASRS Text
Title: FLC ON B737-300 DEPARTING LGA RWY 31 GIVEN EXPEDITE TKOF, AFTER PREVIOUS 2 ACFT HAD TKOF CANCELED. ON BECOMING AIRBORNE AT THE FAR END, THE CREW SAW A DASH-8 AT APPROX 100 FT LNDG ON RWY 22. PIC CONCERNED AND QUESTIONS WHETHER STANDARD SEPARATION EXISTED.
Narrative: 3 AIRPLANES IN A ROW FOR DEP, ACR Z, ACR A AND ACR X (MY AIRPLANE) DEPARTING LGA RWY 31. ACR Z WAS GIVEN TKOF CLRNC, STARTED ROLLING AND HAD TKOF CLRNC CANCELED DUE TO CONFLICT WITH LNDG TFC LNDG RWY 22. ACR A WAS THEN GIVEN TKOF CLRNC ONLY TO HAVE IT CANCELED FOR REASONS UNKNOWN. ACR X WAS THEN GIVEN CLRNC. WE WERE ALREADY SPOOLED, RELEASED BRAKES IMMEDIATELY AND THE CTLR TOLD US WORDS TO THE EFFECT 'EXPEDITE TKOF.' AS WE CLRED THE RWY 31/22 INTXN WE SAW A DASH 8, ACR Y, AT APPROX 100 FT ON FINAL FOR RWY 22. WHILE IT WAS NOT A NEAR MISS, IT WAS LESS THAN COMFORTABLE. I QUESTION IF STANDARD SEPARATION WAS MAINTAINED AS WE WERE GIVEN TKOF CLRNC EVEN BEFORE THE PREVIOUS LNDG TFC HAD CLRED THE RWY 31/22 INTXN. IN VIEW OF THE 2 PREVIOUS MODERATE SPD 'TKOF CLRNC CANCELED' EVENTS I HAVE BEEN INVOLVED IN AND THE ACFT/ACFT VERY NEAR MISS, LGA TWR CONTINUES TO DO BUSINESS IN THEIR VERY CAVALIER, 'NO PROBS HERE' USUAL METHOD OF DOING BUSINESS. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED THAT THE DASH-8 LNDG ON RWY 22 WAS STILL OVER THE WATER WHEN HIS FLT CROSSED RWY 22 ON RWY 31. HE BELIEVES CTLRS AT LGA ARE CAVALIER IN THEIR HANDLING OF TFC AND AT TIMES ARE RUNNING ACFT TOO TIGHT AT THE INTXNS. ALSO SAID CTLR USED SOME PHRASE HE HAD NOT HEARD BEFORE TO INDICATE HE WANTED TO THE CREW TO EXPEDITE TKOF.
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.