37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 849174 |
Time | |
Date | 200908 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LVK.Airport |
State Reference | CA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Flight Phase | Initial Approach |
Person 1 | |
Function | Pilot Flying Single Pilot |
Qualification | Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Private |
Experience | Flight Crew Last 90 Days 10 Flight Crew Total 3010 Flight Crew Type 1300 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC |
Miss Distance | Vertical 20 |
Narrative:
Sun high in sky; visibility 20 miles; ceiling unlimited; distant haze. Tower has an unobstructed view of runway/traffic pattern's and radar. Directed by tower to enter a left base for the left runway; tower then advised there was another airplane in the pattern without radio contact. Did that mean; prior arrangement; light; signals? Later someone apologized for being on the wrong frequency. Landed; taxied back; takeoff; stay in pattern; land; had done about 5 circuits when tower told me that traffic was inbound from san jose and I acknowledged. I was turning from crosswind to downwind when an airplane passed underneath by about 20 ft; possibly the san jose traffic? No other traffic advisories; he turned right to a downwind; had he decided to join the pattern from the juncture of the crosswind and downwind instead of 'abeam the midpoint of the runway' per aim? I continue left turn to the downwind. This began diatribes from the tower; next to impossible trying to communicate. 1) asked did I see the other aircraft? Saw too well; now almost in front of me. Wish I had had a radar update. Conflict usually is resolved by the tower routing the arriving traffic. Usually seamless. 2) directed me to follow the other aircraft; which I was already doing. But it was far too close; so moved to outside and above; slowed for normal spacing; both aircraft completed a normal landing. 3) said that my downwind was too far out. This airport is closed in by homes/noise abatement at each end. The published airport diagram clearly shows this and space is needed for a normal departure and landing. If the tower felt that an adjustment was really needed then why didn't he advise me of this some time during my previous 5 circuits? The aircraft were passing from right to left directly in from of him! Did this 5 times. When the controller became upset he didn't pause long enough between words for a response; happened several times. I acknowledged all that I could. The tower; between loose traffic and near midair; did not seem very collected.
Original NASA ASRS Text
Title: General aviation aircraft in the pattern at LVK experienced conflict with traffic entering downwind; reporter questioned tower procedure and services provided.
Narrative: Sun high in sky; visibility 20 miles; ceiling unlimited; distant haze. Tower has an unobstructed view of runway/traffic pattern's and radar. Directed by Tower to enter a left base for the left runway; Tower then advised there was another airplane in the pattern without radio contact. Did that mean; prior arrangement; light; signals? Later someone apologized for being on the wrong frequency. Landed; taxied back; takeoff; stay in pattern; land; had done about 5 circuits when Tower told me that traffic was inbound from San Jose and I acknowledged. I was turning from crosswind to downwind when an airplane passed underneath by about 20 FT; possibly the San Jose traffic? No other traffic advisories; he turned right to a downwind; had he decided to join the pattern from the juncture of the crosswind and downwind instead of 'abeam the midpoint of the runway' per AIM? I continue left turn to the downwind. This began diatribes from the Tower; next to impossible trying to communicate. 1) Asked did I see the other aircraft? Saw TOO well; now almost in front of me. Wish I had had a radar update. Conflict usually is resolved by the Tower routing the arriving traffic. Usually seamless. 2) Directed me to follow the other aircraft; which I was already doing. But it was far too close; so moved to outside and above; slowed for normal spacing; both aircraft completed a normal landing. 3) Said that MY downwind was too far out. This airport is closed in by homes/noise abatement at each end. The published airport diagram clearly shows this and space is needed for a normal departure and landing. If the Tower felt that an adjustment was really needed then why didn't he advise me of this some time during my previous 5 circuits? The aircraft were passing from right to left directly in from of him! Did this 5 times. When the Controller became upset he didn't pause long enough between words for a response; happened several times. I acknowledged all that I could. The Tower; between loose traffic and near midair; did not seem very collected.
Data retrieved from NASA's ASRS site as of April 2012 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.