 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A cessna 172 and a piper cub have an near midair collision without the pilot of the cessna even knowing about it. The cessna pilot also lands with the piper still on the runway.
| Attributes | |
| ACN | 588622 |
| Time | |
| Date | 200307 |
| Day | Sat |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : bjj.airport |
| State Reference | OH |
| Altitude | agl bound lower : 500 agl bound upper : 800 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | general aviation : personal |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach |
| Route In Use | approach : traffic pattern arrival : vfr |
| Flight Plan | None |
| Aircraft 2 | |
| Operator | general aviation : personal |
| Make Model Name | J3 Cub |
| Operating Under FAR Part | Part 91 |
| Flight Phase | descent : approach |
| Route In Use | approach : traffic pattern |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 16 flight time total : 332 flight time type : 275 |
| ASRS Report | 588622 |
| Person 2 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Events | |
| Anomaly | conflict : nmac non adherence : far |
| Independent Detector | other flight crewa |
| Miss Distance | horizontal : 0 vertical : 50 |
| Supplementary | |
| Problem Areas | Airport Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
Narrative:
I turned base to final for runway 28 at wooster/wayne county airport (bjj). A yellow cub was touching down and proceeded to roll out. He slowed and edged to the left side of the runway at the turnoff. He stopped just prior to my touchdown rather than turning off. Aside from the fact that he was still on the runway when I landed there was no conflict as he was approximately 1000 ft beyond my touchdown point. I could have turned off at the first turnoff, but proceeded to the second turnoff, the one the cub used, so as not to cut in front of him. He pulled off the taxiway and parked and I continued to the runway threshold and took off. It was then that he called me on the unicom and informed me that we had almost collided on final approach. He told me that on the previous landing, he had been on final approach for runway 28 and that he saw a shadow and suddenly I was above him. He broke off his approach and turned out of the final approach course. He then flew an abbreviated pattern and landed. I did a touch-and-go and he landed ahead of me, before I flew the pattern and came in behind him. It wasn't until he called me on the unicom that I was aware that this conflict had occurred. I was directly above him and never saw him. Other planes were in the pattern and I was, so I thought, exercising diligence to stay clear of everyone and aware of their position. The pilot of the cub had a handheld receiver but could not transmit. I believe that the lack of radio reports along with his much slower airspeed were contributing factors. I have no explanation for not seeing a bright yellow airplane, but I didn't. As for touching down before he cleared the runway, I had no excuse. I thought he would be clear before I touched down but he wasn't. In the future, I'll go around if there's any question whatsoever and rely on a better scan in addition to listening for position reports.
Original NASA ASRS Text
Title: A CESSNA 172 AND A PIPER CUB HAVE AN NMAC WITHOUT THE PLT OF THE CESSNA EVEN KNOWING ABOUT IT. THE CESSNA PLT ALSO LANDS WITH THE PIPER STILL ON THE RWY.
Narrative: I TURNED BASE TO FINAL FOR RWY 28 AT WOOSTER/WAYNE COUNTY ARPT (BJJ). A YELLOW CUB WAS TOUCHING DOWN AND PROCEEDED TO ROLL OUT. HE SLOWED AND EDGED TO THE L SIDE OF THE RWY AT THE TURNOFF. HE STOPPED JUST PRIOR TO MY TOUCHDOWN RATHER THAN TURNING OFF. ASIDE FROM THE FACT THAT HE WAS STILL ON THE RWY WHEN I LANDED THERE WAS NO CONFLICT AS HE WAS APPROX 1000 FT BEYOND MY TOUCHDOWN POINT. I COULD HAVE TURNED OFF AT THE FIRST TURNOFF, BUT PROCEEDED TO THE SECOND TURNOFF, THE ONE THE CUB USED, SO AS NOT TO CUT IN FRONT OF HIM. HE PULLED OFF THE TXWY AND PARKED AND I CONTINUED TO THE RWY THRESHOLD AND TOOK OFF. IT WAS THEN THAT HE CALLED ME ON THE UNICOM AND INFORMED ME THAT WE HAD ALMOST COLLIDED ON FINAL APCH. HE TOLD ME THAT ON THE PREVIOUS LNDG, HE HAD BEEN ON FINAL APCH FOR RWY 28 AND THAT HE SAW A SHADOW AND SUDDENLY I WAS ABOVE HIM. HE BROKE OFF HIS APCH AND TURNED OUT OF THE FINAL APCH COURSE. HE THEN FLEW AN ABBREVIATED PATTERN AND LANDED. I DID A TOUCH-AND-GO AND HE LANDED AHEAD OF ME, BEFORE I FLEW THE PATTERN AND CAME IN BEHIND HIM. IT WASN'T UNTIL HE CALLED ME ON THE UNICOM THAT I WAS AWARE THAT THIS CONFLICT HAD OCCURRED. I WAS DIRECTLY ABOVE HIM AND NEVER SAW HIM. OTHER PLANES WERE IN THE PATTERN AND I WAS, SO I THOUGHT, EXERCISING DILIGENCE TO STAY CLR OF EVERYONE AND AWARE OF THEIR POS. THE PLT OF THE CUB HAD A HANDHELD RECEIVER BUT COULD NOT XMIT. I BELIEVE THAT THE LACK OF RADIO RPTS ALONG WITH HIS MUCH SLOWER AIRSPD WERE CONTRIBUTING FACTORS. I HAVE NO EXPLANATION FOR NOT SEEING A BRIGHT YELLOW AIRPLANE, BUT I DIDN'T. AS FOR TOUCHING DOWN BEFORE HE CLRED THE RWY, I HAD NO EXCUSE. I THOUGHT HE WOULD BE CLR BEFORE I TOUCHED DOWN BUT HE WASN'T. IN THE FUTURE, I'LL GO AROUND IF THERE'S ANY QUESTION WHATSOEVER AND RELY ON A BETTER SCAN IN ADDITION TO LISTENING FOR POS RPTS.
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.