 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot of an small aircraft sel took off in front of landing traffic at an uncontrolled airport. The reporter was in the wrong but blamed the other aircraft for making a straight in approach. However, if the other aircraft was first observed on a 2 mi final, it could have previously been in a normal traffic pattern.
| Attributes | |
| ACN | 374712 |
| Time | |
| Date | 199707 |
| Day | Thu |
| Local Time Of Day | 0601 To 1200 |
| Place | |
| Locale Reference | airport : rog |
| State Reference | AR |
| Altitude | agl bound lower : 0 agl bound upper : 100 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Operator | general aviation : personal |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 91 |
| Flight Phase | climbout : takeoff |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | other : unknown |
| Flight Phase | descent : approach landing other |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | other other : other pilot : atp pilot : cfi |
| Experience | flight time last 90 days : 45 flight time total : 5600 flight time type : 1100 |
| ASRS Report | 374712 |
| Person 2 | |
| Function | flight crew : single pilot |
| Events | |
| Anomaly | non adherence : far other anomaly other other spatial deviation |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Miss Distance | horizontal : 3000 vertical : 500 |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
While making final check before entering runway at an uncontrolled airport, heard radio call from aircraft calling for straight-in from 5 mi. I looked and saw a landing light in the distance, estimated at 2 mi. I taxied on the runway and took off without delay. While on takeoff roll I heard radio call from aircraft telling me to expedite. While on downwind departure I noted turbojet or turboprop aircraft on rollout following landing. I advised pilot by radio to use the traffic pattern in the future. Problem: traffic conflict between high speed and low speed aircraft at uncontrolled airport. Solutions: use of standard pattern entry by all aircraft. Use of airport with tower control for aircraft requiring straight-in approachs for economic or other reasons.
Original NASA ASRS Text
Title: PLT OF AN SMA SEL TOOK OFF IN FRONT OF LNDG TFC AT AN UNCTLED ARPT. THE RPTR WAS IN THE WRONG BUT BLAMED THE OTHER ACFT FOR MAKING A STRAIGHT IN APCH. HOWEVER, IF THE OTHER ACFT WAS FIRST OBSERVED ON A 2 MI FINAL, IT COULD HAVE PREVIOUSLY BEEN IN A NORMAL TFC PATTERN.
Narrative: WHILE MAKING FINAL CHK BEFORE ENTERING RWY AT AN UNCTLED ARPT, HEARD RADIO CALL FROM ACFT CALLING FOR STRAIGHT-IN FROM 5 MI. I LOOKED AND SAW A LNDG LIGHT IN THE DISTANCE, ESTIMATED AT 2 MI. I TAXIED ON THE RWY AND TOOK OFF WITHOUT DELAY. WHILE ON TKOF ROLL I HEARD RADIO CALL FROM ACFT TELLING ME TO EXPEDITE. WHILE ON DOWNWIND DEP I NOTED TURBOJET OR TURBOPROP ACFT ON ROLLOUT FOLLOWING LNDG. I ADVISED PLT BY RADIO TO USE THE TFC PATTERN IN THE FUTURE. PROB: TFC CONFLICT BTWN HIGH SPD AND LOW SPD ACFT AT UNCTLED ARPT. SOLUTIONS: USE OF STANDARD PATTERN ENTRY BY ALL ACFT. USE OF ARPT WITH TWR CTL FOR ACFT REQUIRING STRAIGHT-IN APCHS FOR ECONOMIC OR OTHER REASONS.
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.