37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 546155 |
Time | |
Date | 200205 |
Day | Thu |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : prb.airport |
State Reference | CA |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Bonanza 36 |
Operating Under FAR Part | Part 91 |
Flight Phase | landing : roll |
Route In Use | approach : traffic pattern |
Flight Plan | VFR |
Aircraft 2 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : holding |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 42 flight time total : 295 flight time type : 151 |
ASRS Report | 546155 |
Person 2 | |
Affiliation | other |
Function | flight crew : single pilot |
Events | |
Anomaly | ground encounters : gear up landing non adherence : published procedure other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | other |
Supplementary | |
Problem Areas | Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Narrative:
Approaching prb, I received paso robles ASOS and it said wind was 340 degrees, 10 KTS, so I decided to use runway 1. Then I completed descent and approach checklist. I called unicom to ask traffic advisory at 10 NM from the airport, but there was no answer. I announced I would use runway 1 at 5 NM of airport, and I noticed there was no flying traffic around prb airport. After that, I heard a twin cessna was going to use runway 19 for taking off. I thought if I took runway 1 entry, my arrival course might conflict his departure course. So I checked ASOS again and it said wind was variable 6 KTS. I decided to change to runway 19 because wind was ok, and my arrival course did not conflict with his departure course. I entered to right long base runway 19 and announced I was 3 NM for right base. When I finished my announcement, 2 ground traffic started talking about using runway on CTAF. They said the wind was in favor of runway 31 and continued conversation. But they did not say to use runway 31 at this moment, but I thought they would use runway 31 any moment, so I continued monitoring their conversation. When I turned to final on runway 19, I announced I was on final runway 19 while they stopped talking. After that, they started talking again. I kept my attention to their talking. Finally I noticed I did not complete landing checklist. I started landing checklist. Runway 19 was so close that I was forced to finish the checklist in a very short time. When I started to flare, I noticed something was strange. As soon as I tried to advance power, propeller hit the ground, so I stopped advancing power. When aircraft stopped, I tried to make an announcement that I made a gear-up landing and blocked the runway, but I could not do so because smoke was coming from instrument panel. I turned off all switches and management switch off and vacated the aircraft. What I believe caused this incident: I was distraction too much monitoring other aircraft. Consequently, there was not enough time to perform landing checklist properly. To prevent this incident: when I monitor other aircraft's announcement and I have questions, I should ask their intentions. That will help me to take the right course of action. In any case, landing checklist should be completed in the proper manner. If I do not complete landing checklist and have something in doubt, I should make go around.
Original NASA ASRS Text
Title: BEECH B36 PLT LANDED GEAR UP. TFC WATCH DISTR HIM FROM COMPLETING THE BEFORE LNDG CHKLIST.
Narrative: APCHING PRB, I RECEIVED PASO ROBLES ASOS AND IT SAID WIND WAS 340 DEGS, 10 KTS, SO I DECIDED TO USE RWY 1. THEN I COMPLETED DSCNT AND APCH CHKLIST. I CALLED UNICOM TO ASK TFC ADVISORY AT 10 NM FROM THE ARPT, BUT THERE WAS NO ANSWER. I ANNOUNCED I WOULD USE RWY 1 AT 5 NM OF ARPT, AND I NOTICED THERE WAS NO FLYING TFC AROUND PRB ARPT. AFTER THAT, I HEARD A TWIN CESSNA WAS GOING TO USE RWY 19 FOR TAKING OFF. I THOUGHT IF I TOOK RWY 1 ENTRY, MY ARR COURSE MIGHT CONFLICT HIS DEP COURSE. SO I CHKED ASOS AGAIN AND IT SAID WIND WAS VARIABLE 6 KTS. I DECIDED TO CHANGE TO RWY 19 BECAUSE WIND WAS OK, AND MY ARR COURSE DID NOT CONFLICT WITH HIS DEP COURSE. I ENTERED TO R LONG BASE RWY 19 AND ANNOUNCED I WAS 3 NM FOR R BASE. WHEN I FINISHED MY ANNOUNCEMENT, 2 GND TFC STARTED TALKING ABOUT USING RWY ON CTAF. THEY SAID THE WIND WAS IN FAVOR OF RWY 31 AND CONTINUED CONVERSATION. BUT THEY DID NOT SAY TO USE RWY 31 AT THIS MOMENT, BUT I THOUGHT THEY WOULD USE RWY 31 ANY MOMENT, SO I CONTINUED MONITORING THEIR CONVERSATION. WHEN I TURNED TO FINAL ON RWY 19, I ANNOUNCED I WAS ON FINAL RWY 19 WHILE THEY STOPPED TALKING. AFTER THAT, THEY STARTED TALKING AGAIN. I KEPT MY ATTN TO THEIR TALKING. FINALLY I NOTICED I DID NOT COMPLETE LNDG CHKLIST. I STARTED LNDG CHKLIST. RWY 19 WAS SO CLOSE THAT I WAS FORCED TO FINISH THE CHKLIST IN A VERY SHORT TIME. WHEN I STARTED TO FLARE, I NOTICED SOMETHING WAS STRANGE. AS SOON AS I TRIED TO ADVANCE PWR, PROP HIT THE GND, SO I STOPPED ADVANCING PWR. WHEN ACFT STOPPED, I TRIED TO MAKE AN ANNOUNCEMENT THAT I MADE A GEAR-UP LNDG AND BLOCKED THE RWY, BUT I COULD NOT DO SO BECAUSE SMOKE WAS COMING FROM INST PANEL. I TURNED OFF ALL SWITCHES AND MGMNT SWITCH OFF AND VACATED THE ACFT. WHAT I BELIEVE CAUSED THIS INCIDENT: I WAS DISTR TOO MUCH MONITORING OTHER ACFT. CONSEQUENTLY, THERE WAS NOT ENOUGH TIME TO PERFORM LNDG CHKLIST PROPERLY. TO PREVENT THIS INCIDENT: WHEN I MONITOR OTHER ACFT'S ANNOUNCEMENT AND I HAVE QUESTIONS, I SHOULD ASK THEIR INTENTIONS. THAT WILL HELP ME TO TAKE THE RIGHT COURSE OF ACTION. IN ANY CASE, LNDG CHKLIST SHOULD BE COMPLETED IN THE PROPER MANNER. IF I DO NOT COMPLETE LNDG CHKLIST AND HAVE SOMETHING IN DOUBT, I SHOULD MAKE GAR.
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.