B737 flight crew encounter company system information failure at destination airport requiring additional coordination with company and bdl to determine useable, company approach procedure. Dispatch advises 'data drop' was 'not the first time.'

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	514270
Time
Date	200105
Day	Wed
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : bdl.airport
State Reference	CT
Environment
Weather Elements	other
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : y90.tracon
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	ils localizer & glide slope : 33
Flight Phase	descent : approach descent : holding
Route In Use	approach : instrument precision arrival : holding pattern
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : y90.tracon
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	descent : holding descent : approach
Route In Use	arrival : holding pattern
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
ASRS Report	514270
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	aircraft equipment problem : less severe other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	other
Supplementary
Problem Areas	Company Flight Crew Human Performance
Primary Problem	Company

Narrative:

Pulled paperwork in ord at XA00 am central. Field report showed all runways open. We got ATIS at bdl. Showed ILS runway 24 in use along with runway 15. Crew planned on runway 24 ILS due to 4 mi haze WX. Bdl approach brought us around for a slam dunk visual to runway 15. We do not have that approach and requested runway 24, winds were calm. Bdl says runway 24 closed. We then said unable to use runway 15. Wanted ILS to runway 24 or runway 33. Bdl says 60 mins required to use runway 24. Both us and another air carrier held until we figured out what to do. We finally got the ILS to runway 33, turned on and landed. We called bdl operations while holding, did not want to rush and asked what the story was on runway 24. They had listed it on the field reports and it dropped out of the system, system possible closing of runway with both paperwork and ATIS saying runway open. This information should not drop out of system. Safety issue. Company dispatch says not first time it happened.

Original NASA ASRS Text

Title: B737 FLC ENCOUNTER COMPANY SYS INFO FAILURE AT DEST ARPT REQUIRING ADDITIONAL COORD WITH COMPANY AND BDL TO DETERMINE USEABLE, COMPANY APCH PROC. DISPATCH ADVISES 'DATA DROP' WAS 'NOT THE FIRST TIME.'

Narrative: PULLED PAPERWORK IN ORD AT XA00 AM CENTRAL. FIELD RPT SHOWED ALL RWYS OPEN. WE GOT ATIS AT BDL. SHOWED ILS RWY 24 IN USE ALONG WITH RWY 15. CREW PLANNED ON RWY 24 ILS DUE TO 4 MI HAZE WX. BDL APCH BROUGHT US AROUND FOR A SLAM DUNK VISUAL TO RWY 15. WE DO NOT HAVE THAT APCH AND REQUESTED RWY 24, WINDS WERE CALM. BDL SAYS RWY 24 CLOSED. WE THEN SAID UNABLE TO USE RWY 15. WANTED ILS TO RWY 24 OR RWY 33. BDL SAYS 60 MINS REQUIRED TO USE RWY 24. BOTH US AND ANOTHER ACR HELD UNTIL WE FIGURED OUT WHAT TO DO. WE FINALLY GOT THE ILS TO RWY 33, TURNED ON AND LANDED. WE CALLED BDL OPS WHILE HOLDING, DID NOT WANT TO RUSH AND ASKED WHAT THE STORY WAS ON RWY 24. THEY HAD LISTED IT ON THE FIELD RPTS AND IT DROPPED OUT OF THE SYS, SYS POSSIBLE CLOSING OF RWY WITH BOTH PAPERWORK AND ATIS SAYING RWY OPEN. THIS INFO SHOULD NOT DROP OUT OF SYS. SAFETY ISSUE. COMPANY DISPATCH SAYS NOT FIRST TIME IT HAPPENED.

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.