 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
2 air carrier aircraft operating in hnl airspace with very similar or same flight numbers due late arrival of first aircraft. Both aircraft operating for the same company. The company dispatch computer did not catch the conflict
| Attributes | |
| ACN | 201518 |
| Time | |
| Date | 199202 |
| Day | Mon |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : hnl |
| State Reference | HI |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| Aircraft 1 | |
| Controlling Facilities | tracon : maf |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | descent : approach landing other |
| Route In Use | enroute : other oceanic enroute : pacific |
| Flight Plan | IFR |
| Aircraft 2 | |
| Operator | common carrier : air carrier |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | ground : preflight |
| Route In Use | enroute : other oceanic enroute : pacific |
| Flight Plan | IFR |
| Person 1 | |
| Affiliation | company : air carrier |
| Function | other personnel |
| Qualification | other other : other |
| ASRS Report | 201518 |
| Person 2 | |
| Affiliation | company : air carrier |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : atp |
| Events | |
| Anomaly | other anomaly other |
| Independent Detector | other other : unspecified |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Supplementary | |
| Air Traffic Incident | other |
Narrative:
Flight 'back course' was en route to hnl from lax and was running approximately 1:20 behind schedule. Flight 'back course' was estimating a hnl arrival around XX30Z. Flight 'abbc', hnl-fuk was scheduled for a XX30 departure. To meet jcab requirements flight 'abbc' was filed, as always, as flight 'back course'. I did not catch the conflict of 2 flight 'back course's' in hnl airspace at the same time and since the computer only looks at the hnl-fuk flight as 'abbc' I was not given the normal conflict message generated by the computer when 2 flts of the same call sign would be operating in the same airspace.
Original NASA ASRS Text
Title: 2 ACR ACFT OPERATING IN HNL AIRSPACE WITH VERY SIMILAR OR SAME FLT NUMBERS DUE LATE ARR OF FIRST ACFT. BOTH ACFT OPERATING FOR THE SAME COMPANY. THE COMPANY DISPATCH COMPUTER DID NOT CATCH THE CONFLICT
Narrative: FLT 'BC' WAS ENRTE TO HNL FROM LAX AND WAS RUNNING APPROX 1:20 BEHIND SCHEDULE. FLT 'BC' WAS ESTIMATING A HNL ARR AROUND XX30Z. FLT 'ABBC', HNL-FUK WAS SCHEDULED FOR A XX30 DEP. TO MEET JCAB REQUIREMENTS FLT 'ABBC' WAS FILED, AS ALWAYS, AS FLT 'BC'. I DID NOT CATCH THE CONFLICT OF 2 FLT 'BC'S' IN HNL AIRSPACE AT THE SAME TIME AND SINCE THE COMPUTER ONLY LOOKS AT THE HNL-FUK FLT AS 'ABBC' I WAS NOT GIVEN THE NORMAL CONFLICT MESSAGE GENERATED BY THE COMPUTER WHEN 2 FLTS OF THE SAME CALL SIGN WOULD BE OPERATING IN THE SAME AIRSPACE.
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.