37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 529670 |
Time | |
Date | 200111 |
Day | Fri |
Local Time Of Day | 1801 To 2400 |
Place | |
Locale Reference | airport : bli.airport |
State Reference | WA |
Altitude | msl single value : 2400 |
Environment | |
Light | Night |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Flight Plan | VFR |
Person 1 | |
Affiliation | other |
Function | instruction : instructor |
Qualification | pilot : multi engine pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 85 flight time total : 1999 flight time type : 400 |
ASRS Report | 529690 |
Person 2 | |
Affiliation | other |
Function | instruction : trainee |
Events | |
Anomaly | other anomaly other |
Independent Detector | other flight crewa other flight crewb other other : 3 |
Resolutory Action | controller : provided flight assist controller : issued new clearance none taken : detected after the fact |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
This was a night training flight from paine field, everett, wa, to bli, wa, about 50 NM. The flight was VFR. There were some scattered clouds about 1900 ft between whidbey island and just north of skagit bayview airport. We were at 4500 ft. It was clear on top of the 1900 ft scattered. Upon reaching bli, I thought I knew where I was and I didn't pay attention (nor believe them) to my instruments. I have been there several times and once before at night. The northern bay area and the bli bay look exactly alike (especially at night!). We flew around looking for the airport. We had plenty of fuel (over 4 hours) and it was a very clear night at bli. We found an airport north, but I knew it was not bli because of runway alignment. (I turned the aircraft toward the runway at 2400 ft.) meanwhile, I was trying to tune into the VOR which the student set to the wrong VOR. I did not notice until I was trying to see where we were. We had GPS, but I am not very familiar with this instrument. It was set to GPS and not navigation. (This is what I believe.) that is why I couldn't receive the navigation signal. Meanwhile, the student pilot brought his wife with him and after takeoff from pae she started screaming she wanted to go back to pae. She had been flying with us before during the day and had no problem. The student calmed her down and we continued. I tried to convince him to go back to pae. When we were descending into bli she started screaming. Again she wanted to go home! And I believe this was the major cause of the distraction. When we were flying northwest we flew into boundary bay airspace and we were at 2400 ft. We never had any close conflict with any other aircraft. We were in contact with bli tower and he asked us to 'identify' and told us we were 18 NM northwest from bli airport. He then vectored us toward the airport. At that time I had figured out where we were from the whatcom VOR. We flew into bli with no further incident. Landed and returned to pae field with no further problems. If I were to experience a similar situation again, I would immediately terminate the flight and land as soon as possible. I would also believe and trust my instruments. After an 8 yr absence, I returned to flying in february to full time. Even with flying experience, continuous distrs in the cockpit can lead to potential problems.
Original NASA ASRS Text
Title: C172 INSTRUCTOR BECAME DISORIENTED ON A NIGHT FLT. THE STUDENT'S WIFE, PAX, BECAME HYSTERICAL AND BEGAN SCREAMING.
Narrative: THIS WAS A NIGHT TRAINING FLT FROM PAINE FIELD, EVERETT, WA, TO BLI, WA, ABOUT 50 NM. THE FLT WAS VFR. THERE WERE SOME SCATTERED CLOUDS ABOUT 1900 FT BTWN WHIDBEY ISLAND AND JUST N OF SKAGIT BAYVIEW ARPT. WE WERE AT 4500 FT. IT WAS CLR ON TOP OF THE 1900 FT SCATTERED. UPON REACHING BLI, I THOUGHT I KNEW WHERE I WAS AND I DIDN'T PAY ATTN (NOR BELIEVE THEM) TO MY INSTS. I HAVE BEEN THERE SEVERAL TIMES AND ONCE BEFORE AT NIGHT. THE NORTHERN BAY AREA AND THE BLI BAY LOOK EXACTLY ALIKE (ESPECIALLY AT NIGHT!). WE FLEW AROUND LOOKING FOR THE ARPT. WE HAD PLENTY OF FUEL (OVER 4 HRS) AND IT WAS A VERY CLR NIGHT AT BLI. WE FOUND AN ARPT N, BUT I KNEW IT WAS NOT BLI BECAUSE OF RWY ALIGNMENT. (I TURNED THE ACFT TOWARD THE RWY AT 2400 FT.) MEANWHILE, I WAS TRYING TO TUNE INTO THE VOR WHICH THE STUDENT SET TO THE WRONG VOR. I DID NOT NOTICE UNTIL I WAS TRYING TO SEE WHERE WE WERE. WE HAD GPS, BUT I AM NOT VERY FAMILIAR WITH THIS INST. IT WAS SET TO GPS AND NOT NAV. (THIS IS WHAT I BELIEVE.) THAT IS WHY I COULDN'T RECEIVE THE NAV SIGNAL. MEANWHILE, THE STUDENT PLT BROUGHT HIS WIFE WITH HIM AND AFTER TKOF FROM PAE SHE STARTED SCREAMING SHE WANTED TO GO BACK TO PAE. SHE HAD BEEN FLYING WITH US BEFORE DURING THE DAY AND HAD NO PROB. THE STUDENT CALMED HER DOWN AND WE CONTINUED. I TRIED TO CONVINCE HIM TO GO BACK TO PAE. WHEN WE WERE DSNDING INTO BLI SHE STARTED SCREAMING. AGAIN SHE WANTED TO GO HOME! AND I BELIEVE THIS WAS THE MAJOR CAUSE OF THE DISTR. WHEN WE WERE FLYING NW WE FLEW INTO BOUNDARY BAY AIRSPACE AND WE WERE AT 2400 FT. WE NEVER HAD ANY CLOSE CONFLICT WITH ANY OTHER ACFT. WE WERE IN CONTACT WITH BLI TWR AND HE ASKED US TO 'IDENT' AND TOLD US WE WERE 18 NM NW FROM BLI ARPT. HE THEN VECTORED US TOWARD THE ARPT. AT THAT TIME I HAD FIGURED OUT WHERE WE WERE FROM THE WHATCOM VOR. WE FLEW INTO BLI WITH NO FURTHER INCIDENT. LANDED AND RETURNED TO PAE FIELD WITH NO FURTHER PROBS. IF I WERE TO EXPERIENCE A SIMILAR SIT AGAIN, I WOULD IMMEDIATELY TERMINATE THE FLT AND LAND ASAP. I WOULD ALSO BELIEVE AND TRUST MY INSTS. AFTER AN 8 YR ABSENCE, I RETURNED TO FLYING IN FEBRUARY TO FULL TIME. EVEN WITH FLYING EXPERIENCE, CONTINUOUS DISTRS IN THE COCKPIT CAN LEAD TO POTENTIAL PROBS.
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.