37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 511652 |
Time | |
Date | 200105 |
Day | Thu |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : zzz.airport |
State Reference | US |
Altitude | msl single value : 28000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zbw.artcc artcc : zab.artcc |
Make Model Name | Do 328 TP (Turboprop) |
Operating Under FAR Part | Part 121 |
Flight Phase | cruise : level |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Experience | flight time last 90 days : 285 flight time total : 10000 flight time type : 4100 |
ASRS Report | 511652 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : atp pilot : cfi |
Experience | flight time last 90 days : 240 flight time total : 3800 flight time type : 1500 |
ASRS Report | 511342 |
Events | |
Anomaly | aircraft equipment problem : critical maintenance problem : improper documentation non adherence : far non adherence : published procedure other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : cabin door warining other flight crewa other flight crewb |
Resolutory Action | none taken : anomaly accepted |
Consequence | Other |
Factors | |
Maintenance | performance deficiency : non compliance with legal requirements performance deficiency : logbook entry performance deficiency : repair |
Supplementary | |
Problem Areas | Flight Crew Human Performance Maintenance Human Performance Aircraft |
Primary Problem | Flight Crew Human Performance |
Narrative:
In brief, after leveling off at FL280, the first officer and I configured the aircraft for cruise flight and settled in for the remainder of the flight to ZZZ. Approximately 30-40 mi from bos, we were alerted by a triple chime and master warning that the main cabin door was not secure. Looking out of the captain's left side window, I could see that the main cabin door was not open. That, coupled with the lack of 'cabin altitude' warning, led me to believe that the door was in fact closed. At this point, we ran the required QRH checklist, followed by my xferring control to the first officer so that I could contact maintenance control. I alerted the flight attendant to the potential problem and requested that she look, not touch, the main cabin door to see if it appeared to be closed and locked. She indicated to me that it appeared to be normal. After trying to raise commercial radio on 3 different frequencys, I secured a radio-to-phone relay with company operations. While speaking with company/maintenance control, the first officer, at my direction, began a descent to a lower altitude. While awaiting a response from a radio exchange, the indications of the problem disappeared. I passed the information along to maintenance control and began to discuss the incident with the first officer and at the same time review the system pages for information as to the possible causes of the anomaly. The cabin pressure control selector panel page showed that the aircraft was pressurizing at a slightly higher than normal rate. I reached up to point at the cabin pressure control selector panel while speaking with the first officer. As I was pointing to the panel, I tapped it with the tip of my index finger and the trend on the system page reversed and settled into normal parameters. Conferring with my crew, it was concluded we could find no reason for the now absent, yet spurious indications and we agreed to continue the flight with heightened vigilance. We landed in ZZZ without further incident. After offloading the passenger, I called maintenance control via cell phone and discussed the anomaly. We agreed that this anomaly, for lack of a better description, was probably one of the many, 'computer reboot required/stray electron' problems that have always infected these airplanes. In my conversation with maintenance control, I indicated that I would discuss this anomaly with the crew picking up the aircraft. About this time, the new crew arrived and I discussed the situation with the new captain. I discussed the possible need for a maintenance entry in the aircraft log and after the new captain called maintenance control and conferred with them, we all agreed that in the absence of a problem or any indication thereof, that a logbook entry was not warranted.
Original NASA ASRS Text
Title: A DORNIER IN CRUISE AT FL280 EXPERIENCES A DOOR WARNING. ACFT DSNDED PER PROCS AND MAINT ADVISED. NO LOGBOOK ENTRY MADE ON INCIDENT.
Narrative: IN BRIEF, AFTER LEVELING OFF AT FL280, THE FO AND I CONFIGURED THE ACFT FOR CRUISE FLT AND SETTLED IN FOR THE REMAINDER OF THE FLT TO ZZZ. APPROX 30-40 MI FROM BOS, WE WERE ALERTED BY A TRIPLE CHIME AND MASTER WARNING THAT THE MAIN CABIN DOOR WAS NOT SECURE. LOOKING OUT OF THE CAPT'S L SIDE WINDOW, I COULD SEE THAT THE MAIN CABIN DOOR WAS NOT OPEN. THAT, COUPLED WITH THE LACK OF 'CABIN ALT' WARNING, LED ME TO BELIEVE THAT THE DOOR WAS IN FACT CLOSED. AT THIS POINT, WE RAN THE REQUIRED QRH CHKLIST, FOLLOWED BY MY XFERRING CTL TO THE FO SO THAT I COULD CONTACT MAINT CTL. I ALERTED THE FLT ATTENDANT TO THE POTENTIAL PROB AND REQUESTED THAT SHE LOOK, NOT TOUCH, THE MAIN CABIN DOOR TO SEE IF IT APPEARED TO BE CLOSED AND LOCKED. SHE INDICATED TO ME THAT IT APPEARED TO BE NORMAL. AFTER TRYING TO RAISE COMMERCIAL RADIO ON 3 DIFFERENT FREQS, I SECURED A RADIO-TO-PHONE RELAY WITH COMPANY OPS. WHILE SPEAKING WITH COMPANY/MAINT CTL, THE FO, AT MY DIRECTION, BEGAN A DSCNT TO A LOWER ALT. WHILE AWAITING A RESPONSE FROM A RADIO EXCHANGE, THE INDICATIONS OF THE PROB DISAPPEARED. I PASSED THE INFO ALONG TO MAINT CTL AND BEGAN TO DISCUSS THE INCIDENT WITH THE FO AND AT THE SAME TIME REVIEW THE SYS PAGES FOR INFO AS TO THE POSSIBLE CAUSES OF THE ANOMALY. THE CABIN PRESSURE CTL SELECTOR PANEL PAGE SHOWED THAT THE ACFT WAS PRESSURIZING AT A SLIGHTLY HIGHER THAN NORMAL RATE. I REACHED UP TO POINT AT THE CABIN PRESSURE CTL SELECTOR PANEL WHILE SPEAKING WITH THE FO. AS I WAS POINTING TO THE PANEL, I TAPPED IT WITH THE TIP OF MY INDEX FINGER AND THE TREND ON THE SYS PAGE REVERSED AND SETTLED INTO NORMAL PARAMETERS. CONFERRING WITH MY CREW, IT WAS CONCLUDED WE COULD FIND NO REASON FOR THE NOW ABSENT, YET SPURIOUS INDICATIONS AND WE AGREED TO CONTINUE THE FLT WITH HEIGHTENED VIGILANCE. WE LANDED IN ZZZ WITHOUT FURTHER INCIDENT. AFTER OFFLOADING THE PAX, I CALLED MAINT CTL VIA CELL PHONE AND DISCUSSED THE ANOMALY. WE AGREED THAT THIS ANOMALY, FOR LACK OF A BETTER DESCRIPTION, WAS PROBABLY ONE OF THE MANY, 'COMPUTER REBOOT REQUIRED/STRAY ELECTRON' PROBS THAT HAVE ALWAYS INFECTED THESE AIRPLANES. IN MY CONVERSATION WITH MAINT CTL, I INDICATED THAT I WOULD DISCUSS THIS ANOMALY WITH THE CREW PICKING UP THE ACFT. ABOUT THIS TIME, THE NEW CREW ARRIVED AND I DISCUSSED THE SIT WITH THE NEW CAPT. I DISCUSSED THE POSSIBLE NEED FOR A MAINT ENTRY IN THE ACFT LOG AND AFTER THE NEW CAPT CALLED MAINT CTL AND CONFERRED WITH THEM, WE ALL AGREED THAT IN THE ABSENCE OF A PROB OR ANY INDICATION THEREOF, THAT A LOGBOOK ENTRY WAS NOT WARRANTED.
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.