37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 474929 |
Time | |
Date | 200006 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : zph.airport |
State Reference | FL |
Altitude | agl single value : 0 |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | ground : taxi |
Flight Plan | None |
Aircraft 2 | |
Operator | general aviation : personal |
Make Model Name | Sail Plane |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach |
Person 1 | |
Affiliation | other |
Function | flight crew : single pilot |
Qualification | pilot : private |
Experience | flight time last 90 days : 10 flight time total : 360 flight time type : 100 |
ASRS Report | 474629 |
Person 2 | |
Affiliation | other |
Function | observation : passenger other personnel other |
Qualification | other other : pax pilot : private |
Events | |
Anomaly | conflict : ground critical ground encounters other incursion : runway non adherence : far non adherence : published procedure |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | flight crew : took evasive action none taken : detected after the fact other |
Miss Distance | horizontal : 30 vertical : 20 |
Supplementary | |
Problem Areas | FAA Airport Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
At approximately XA00 on sunday june 2000 I had just landed my aircraft, a cessna 172, on runway 22 in zephyrhills airport. In the right seat was my wife, also a private pilot. I turned off runway 22 onto a taxiway and proceeded ese where we planned to change seats near the parachute facility on the field. Our taxiway crossed the threshold of runway 36 prior to the parachute area. As the taxiway approached the intersection of runway 36 my wife and I searched for landing traffic on runway 36, as well looking for any parachuters in the area. Having heard no radio traffic reports and seeing no approaching aircraft, I crossed the line onto runway 36. I then saw a sailplane on very short final who appeared to be intending ot land on the grassy area short of the approach end of runway 36. The sailplane was about three ft over the grass and about 30 ft from the threshold of runway 36 when I first saw him. I immediately braked to a stop, with my nose wheel over onto the active runway 36. My wings and tail section were still on the taxiway side of the runway margin lines when my aircraft stopped. The sailplane pilot then initiated a climb and passed in front and about 20 ft above my aircraft and then landed uneventfully on the 36 centerline when well past the taxiway runway intersection. Contributing factors: since both my wife, (also a pilot), and myself actively scanned for landing traffic before proceeding onto the active runway, I can only speculate as to what extent the following factors my have played in my inability to visually acquire the traffic in time to stop short of the runway. 1 the small cross section of the sailplane. When viewed 'head on', a sailplane presents a very small visual target. 2 a large forest fire burned to the southeast of the airport making the sky gray with smoke. This may have reduced the contrast between the aircraft and the sky. 3 since the sailplane appeared to be landing in the grass short of the runway threshold, his location on short final may have been in and atypical position in reference to the horizon, thus making it more difficult to visually acquire. The sailplane may have been below the horizon-line, (trees), as seen from my plane as we approached the runway intersection. The sailplane was definitely well below the horizon-line when I first saw him. The sailplane's inability to make a radio position report in the pattern eliminated an important clue to traffic position awareness for all pilots utilizing the airport. Corrective action: 1 my application of brakes bringing my aircraft to a stop prior to a potential collision point on the runway. 2 the sailplane pilot's ascending maneuver to avoid a potential accident if my aircraft had not stopped.
Original NASA ASRS Text
Title: C172 AND A SAILPLANE ALMOST COLLIDED AT ZPH.
Narrative: AT APPROX XA00 ON SUNDAY JUNE 2000 I HAD JUST LANDED MY ACFT, A CESSNA 172, ON RWY 22 IN ZEPHYRHILLS ARPT. IN THE R SEAT WAS MY WIFE, ALSO A PRIVATE PLT. I TURNED OFF RWY 22 ONTO A TXWY AND PROCEEDED ESE WHERE WE PLANNED TO CHANGE SEATS NEAR THE PARACHUTE FACILITY ON THE FIELD. OUR TXWY CROSSED THE THRESHOLD OF RWY 36 PRIOR TO THE PARACHUTE AREA. AS THE TXWY APCHED THE INTXN OF RWY 36 MY WIFE AND I SEARCHED FOR LNDG TFC ON RWY 36, AS WELL LOOKING FOR ANY PARACHUTERS IN THE AREA. HAVING HEARD NO RADIO TFC RPTS AND SEEING NO APCHING ACFT, I CROSSED THE LINE ONTO RWY 36. I THEN SAW A SAILPLANE ON VERY SHORT FINAL WHO APPEARED TO BE INTENDING OT LAND ON THE GRASSY AREA SHORT OF THE APCH END OF RWY 36. THE SAILPLANE WAS ABOUT THREE FT OVER THE GRASS AND ABOUT 30 FT FROM THE THRESHOLD OF RWY 36 WHEN I FIRST SAW HIM. I IMMEDIATELY BRAKED TO A STOP, WITH MY NOSE WHEEL OVER ONTO THE ACTIVE RWY 36. MY WINGS AND TAIL SECTION WERE STILL ON THE TXWY SIDE OF THE RWY MARGIN LINES WHEN MY ACFT STOPPED. THE SAILPLANE PLT THEN INITIATED A CLIMB AND PASSED IN FRONT AND ABOUT 20 FT ABOVE MY ACFT AND THEN LANDED UNEVENTFULLY ON THE 36 CTRLINE WHEN WELL PAST THE TXWY RWY INTXN. CONTRIBUTING FACTORS: SINCE BOTH MY WIFE, (ALSO A PLT), AND MYSELF ACTIVELY SCANNED FOR LNDG TFC BEFORE PROCEEDING ONTO THE ACTIVE RWY, I CAN ONLY SPECULATE AS TO WHAT EXTENT THE FOLLOWING FACTORS MY HAVE PLAYED IN MY INABILITY TO VISUALLY ACQUIRE THE TFC IN TIME TO STOP SHORT OF THE RWY. 1 THE SMALL CROSS SECTION OF THE SAILPLANE. WHEN VIEWED 'HEAD ON', A SAILPLANE PRESENTS A VERY SMALL VISUAL TARGET. 2 A LARGE FOREST FIRE BURNED TO THE SOUTHEAST OF THE ARPT MAKING THE SKY GRAY WITH SMOKE. THIS MAY HAVE REDUCED THE CONTRAST BETWEEN THE ACFT AND THE SKY. 3 SINCE THE SAILPLANE APPEARED TO BE LNDG IN THE GRASS SHORT OF THE RWY THRESHOLD, HIS LOCATION ON SHORT FINAL MAY HAVE BEEN IN AND ATYPICAL POSITION IN REFERENCE TO THE HORIZON, THUS MAKING IT MORE DIFFICULT TO VISUALLY ACQUIRE. THE SAILPLANE MAY HAVE BEEN BELOW THE HORIZON-LINE, (TREES), AS SEEN FROM MY PLANE AS WE APCHED THE RWY INTXN. THE SAILPLANE WAS DEFINITELY WELL BELOW THE HORIZON-LINE WHEN I FIRST SAW HIM. THE SAILPLANE'S INABILITY TO MAKE A RADIO POS RPT IN THE PATTERN ELIMINATED AN IMPORTANT CLUE TO TFC POS AWARENESS FOR ALL PLTS UTILIZING THE ARPT. CORRECTIVE ACTION: 1 MY APPLICATION OF BRAKES BRINGING MY ACFT TO A STOP PRIOR TO A POTENTIAL COLLISION POINT ON THE RWY. 2 THE SAILPLANE PLT'S ASCENDING MANEUVER TO AVOID A POTENTIAL ACCIDENT IF MY ACFT HAD NOT STOPPED.
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.