37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1095992 |
Time | |
Date | 201306 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | SCT.TRACON |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | B737-700 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Person 1 | |
Function | Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 125 Flight Crew Type 11000 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
Another carrier was told to line up and wait on runway 24R after being asked if he could accept that runway and he said yes. Suspect he did not change runway in his navigation database. We were told to maintain visual separation and cleared for takeoff on runway 24L right after the other carrier was cleared for takeoff on 24R. After takeoff; he started to drift toward us and I started altering course slightly left to stay away from him. About that time; we got the RA and complied. Either he didn't switch runway in his database or ATC gave an incorrect clearance to one or both of us. Departure seemed like they had no idea why we were both cleared for takeoff nearly in formation. I am curious myself as after both dlrey and fabra the route takes both planes to enney. We maintained visual separation until the RA but as we were basically cleared to takeoff on very close parallel runways at the same time we were very close to start with. We expected the other carrier or us would be given a turn away from each other after takeoff.
Original NASA ASRS Text
Title: LAX air carrier departure described a developing conflict with parallel runway departure traffic after takeoff; the reporter suspecting the conflicting aircraft may not have changed database after a last minute runway change.
Narrative: Another carrier was told to line up and wait on Runway 24R after being asked if he could accept that runway and he said yes. Suspect he did not change runway in his NAV database. We were told to maintain visual separation and cleared for takeoff on Runway 24L right after the other carrier was cleared for takeoff on 24R. After takeoff; he started to drift toward us and I started altering course slightly left to stay away from him. About that time; we got the RA and complied. Either he didn't switch runway in his database or ATC gave an incorrect clearance to one or both of us. Departure seemed like they had no idea why we were both cleared for takeoff nearly in formation. I am curious myself as after both DLREY and FABRA the route takes both planes to ENNEY. We maintained visual separation until the RA but as we were basically cleared to takeoff on very close parallel runways at the same time we were very close to start with. We expected the other carrier or us would be given a turn away from each other after takeoff.
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.