![]() |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
| Attributes | |
| ACN | 268775 |
| Time | |
| Date | 199403 |
| Day | Fri |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : lal |
| State Reference | FL |
| Altitude | agl bound lower : 0 agl bound upper : 0 |
| 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 | landing other |
| Flight Plan | VFR |
| Aircraft 2 | |
| Operator | other |
| Make Model Name | Phantom II (F-4) |
| Operating Under FAR Part | Part 91 |
| Flight Phase | landing other other |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : cfi pilot : flight engineer pilot : atp |
| Experience | flight time last 90 days : 120 flight time total : 10700 flight time type : 900 |
| ASRS Report | 268775 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : captain oversight : pic |
| Qualification | pilot : instrument pilot : commercial |
| Events | |
| Anomaly | conflict : ground less severe incursion : landing without clearance |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : unable |
| Consequence | Other |
| Supplementary | |
| Primary Problem | Flight Crew Human Performance |
| Air Traffic Incident | Pilot Deviation |
Narrative:
Flew a no-radio airplane to the sun 'north fun fly-in. I contacted the lal tower, via telephone, one and a half hours before occurrence for permission to land, no-radio at lal and what procedure to use. Estimated time of arrival. Procedure to use and permission to land no-radio were discussed and granted. Upon arrival to lal, 2 af-4C phantom ii jets were conducting multiple passes down runway. When the F-4S set up to land, I planned to follow behind and land on runway as told by earlier telephone conversation. Number one F-4 landed, but #2 went around. Without light signal, I landed where previously instructed and cleared runway where instructed. While on rollout, the #2 F-4 passed overhead at low altitude and created a tremendous amount of turbulence. At no time did I feel I would have trouble controling aircraft but believed a pilot with less experience might. Problems: never received green light (or any light signal) while in pattern. Possibly, the controllers were busy watching the RF-4. Intermix of high speed versus low speed conflict. As a former air force pilot, I'm familiar with these problems. Arrival procedure discussed on telephone worked well, but I should have been told to expect high speed traffic upon arrival. Any haze or obscuration could have created a dangerous situation. Solutions: keep head on swivel. Sun 'north fun arrival procedures should be active several days before actual fly-in starts, not one or two days before as is current policy.
Original NASA ASRS Text
Title: SMA LANDS AT SPECIAL EVENT ARPT WITHOUT LIGHT SIGNAL BTWN 2 MIL FGTS.
Narrative: FLEW A NO-RADIO AIRPLANE TO THE SUN 'N FUN FLY-IN. I CONTACTED THE LAL TWR, VIA TELEPHONE, ONE AND A HALF HRS BEFORE OCCURRENCE FOR PERMISSION TO LAND, NO-RADIO AT LAL AND WHAT PROC TO USE. ESTIMATED TIME OF ARR. PROC TO USE AND PERMISSION TO LAND NO-RADIO WERE DISCUSSED AND GRANTED. UPON ARR TO LAL, 2 AF-4C PHANTOM II JETS WERE CONDUCTING MULTIPLE PASSES DOWN RWY. WHEN THE F-4S SET UP TO LAND, I PLANNED TO FOLLOW BEHIND AND LAND ON RWY AS TOLD BY EARLIER TELEPHONE CONVERSATION. NUMBER ONE F-4 LANDED, BUT #2 WENT AROUND. WITHOUT LIGHT SIGNAL, I LANDED WHERE PREVIOUSLY INSTRUCTED AND CLRED RWY WHERE INSTRUCTED. WHILE ON ROLLOUT, THE #2 F-4 PASSED OVERHEAD AT LOW ALT AND CREATED A TREMENDOUS AMOUNT OF TURB. AT NO TIME DID I FEEL I WOULD HAVE TROUBLE CTLING ACFT BUT BELIEVED A PLT WITH LESS EXPERIENCE MIGHT. PROBLEMS: NEVER RECEIVED GREEN LIGHT (OR ANY LIGHT SIGNAL) WHILE IN PATTERN. POSSIBLY, THE CTLRS WERE BUSY WATCHING THE RF-4. INTERMIX OF HIGH SPD VERSUS LOW SPD CONFLICT. AS A FORMER AIR FORCE PLT, I'M FAMILIAR WITH THESE PROBS. ARR PROC DISCUSSED ON TELEPHONE WORKED WELL, BUT I SHOULD HAVE BEEN TOLD TO EXPECT HIGH SPD TFC UPON ARR. ANY HAZE OR OBSCURATION COULD HAVE CREATED A DANGEROUS SIT. SOLUTIONS: KEEP HEAD ON SWIVEL. SUN 'N FUN ARR PROCS SHOULD BE ACTIVE SEVERAL DAYS BEFORE ACTUAL FLY-IN STARTS, NOT ONE OR TWO DAYS BEFORE AS IS CURRENT POLICY.
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.