37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 333486 |
Time | |
Date | 199604 |
Day | Wed |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : laf |
State Reference | IN |
Altitude | msl bound lower : 1600 msl bound upper : 1600 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | artcc : zid tower : laf |
Operator | general aviation : instructional |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 91 |
Flight Phase | descent : approach landing other |
Route In Use | arrival other |
Flight Plan | None |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Merlin IIB |
Operating Under FAR Part | Part 121 |
Flight Phase | descent : approach landing other |
Route In Use | arrival other |
Flight Plan | IFR |
Person 1 | |
Affiliation | Other |
Function | instruction : instructor |
Qualification | pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 200 flight time total : 1275 flight time type : 1000 |
ASRS Report | 333486 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp |
Events | |
Anomaly | conflict : nmac other anomaly other |
Independent Detector | other flight crewa |
Resolutory Action | controller : issued new clearance flight crew : took evasive action other |
Consequence | Other |
Miss Distance | horizontal : 400 vertical : 300 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Narrative:
I was flying with a student working on crosswind lndgs on runway 23 at laf, when the pattern began to fill up with traffic coming in to land. Tower switched us to runway 28 (favored runway by the wind) until everyone else landed. Our traffic was called as the second cadet on a 3 mi final, which was their correct position. We reported both on final in sight and were told to follow the second cadet. About 5 seconds later, tower was talking to someone on the opposing (left) downwind, and I spotted what appeared to be a metroliner on a high 3 1/2 mi final for runway 28. When I got a break on the frequency, I asked tower, 'tower, small aircraft X, who's the guy on a high final for runway 28, about 3 1/2 mi out?' tower misunderstood, and thinking that I had lost my traffic to follow, re-reported their position to us. My mistake was not telling that it appeared to be a metroliner on the initial call. I then reported this on my second call, and they said they were expecting a metroliner any time, but they weren't talking to him and asked me for his position. I gave them his position as 'above small aircraft Z' (my traffic to follow) and slightly left of them on final for runway 28. About 5-10 seconds later (it seemed like a long time), the metroliner made his initial call, apologizing for his late call, and said that center had just given him a frequency change. This is a fairly common problem here at laf. ZID forgets that we have a traffic pattern and intensive student training here, and vectors IFR traffic into our pattern. They cannot see anyone reliably below 4000 ft MSL, which is about 3500 ft AGL. They either need to turn IFR inbounds over to our tower earlier, or we need a radar here. There were 5 in the pattern at the time -- me in right traffic, and 4 on the left side, and both of the ones on final at the time were full stop. Tower made the metroliner go around and come back into the pattern as anything else would have made 3 other airplanes go around. This must be frustrating to the metropolitan crew, since they didn't make the mistake in the first place.
Original NASA ASRS Text
Title: INSTRUCTOR PLT ALERTLY ADVISED LAF TWR REGARDING THE POS OF A METROLINER ON A 3-4 MI FINAL, BUT NOT IN COM WITH THEM. ATC HAD ARR INFO ON THE METROLINER, BUT WAS NOT AWARE THAT IT WAS ON FINAL APCH, THAT CLOSE, AND STILL ON ZID FREQ. LAF ATCT DOES NOT HAVE RADAR FOR TFC SEQUENCING.
Narrative: I WAS FLYING WITH A STUDENT WORKING ON XWIND LNDGS ON RWY 23 AT LAF, WHEN THE PATTERN BEGAN TO FILL UP WITH TFC COMING IN TO LAND. TWR SWITCHED US TO RWY 28 (FAVORED RWY BY THE WIND) UNTIL EVERYONE ELSE LANDED. OUR TFC WAS CALLED AS THE SECOND CADET ON A 3 MI FINAL, WHICH WAS THEIR CORRECT POS. WE RPTED BOTH ON FINAL IN SIGHT AND WERE TOLD TO FOLLOW THE SECOND CADET. ABOUT 5 SECONDS LATER, TWR WAS TALKING TO SOMEONE ON THE OPPOSING (L) DOWNWIND, AND I SPOTTED WHAT APPEARED TO BE A METROLINER ON A HIGH 3 1/2 MI FINAL FOR RWY 28. WHEN I GOT A BREAK ON THE FREQ, I ASKED TWR, 'TWR, SMA X, WHO'S THE GUY ON A HIGH FINAL FOR RWY 28, ABOUT 3 1/2 MI OUT?' TWR MISUNDERSTOOD, AND THINKING THAT I HAD LOST MY TFC TO FOLLOW, RE-RPTED THEIR POS TO US. MY MISTAKE WAS NOT TELLING THAT IT APPEARED TO BE A METROLINER ON THE INITIAL CALL. I THEN RPTED THIS ON MY SECOND CALL, AND THEY SAID THEY WERE EXPECTING A METROLINER ANY TIME, BUT THEY WEREN'T TALKING TO HIM AND ASKED ME FOR HIS POS. I GAVE THEM HIS POS AS 'ABOVE SMA Z' (MY TFC TO FOLLOW) AND SLIGHTLY L OF THEM ON FINAL FOR RWY 28. ABOUT 5-10 SECONDS LATER (IT SEEMED LIKE A LONG TIME), THE METROLINER MADE HIS INITIAL CALL, APOLOGIZING FOR HIS LATE CALL, AND SAID THAT CTR HAD JUST GIVEN HIM A FREQ CHANGE. THIS IS A FAIRLY COMMON PROB HERE AT LAF. ZID FORGETS THAT WE HAVE A TFC PATTERN AND INTENSIVE STUDENT TRAINING HERE, AND VECTORS IFR TFC INTO OUR PATTERN. THEY CANNOT SEE ANYONE RELIABLY BELOW 4000 FT MSL, WHICH IS ABOUT 3500 FT AGL. THEY EITHER NEED TO TURN IFR INBOUNDS OVER TO OUR TWR EARLIER, OR WE NEED A RADAR HERE. THERE WERE 5 IN THE PATTERN AT THE TIME -- ME IN R TFC, AND 4 ON THE L SIDE, AND BOTH OF THE ONES ON FINAL AT THE TIME WERE FULL STOP. TWR MADE THE METROLINER GAR AND COME BACK INTO THE PATTERN AS ANYTHING ELSE WOULD HAVE MADE 3 OTHER AIRPLANES GAR. THIS MUST BE FRUSTRATING TO THE METRO CREW, SINCE THEY DIDN'T MAKE THE MISTAKE IN THE FIRST PLACE.
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.