|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||1201 To 1800|
|Locale Reference||airport : fws|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Operator||general aviation : instructional|
|Make Model Name||Small Aircraft, High Wing, 1 Eng, Fixed Gear|
|Flight Phase||climbout : takeoff|
|Operator||general aviation : personal|
|Make Model Name||Small Transport, Low Wing, 2 Recip Eng|
|Flight Phase||landing : go around|
|Qualification||pilot : cfi|
|Experience||flight time last 90 days : 200|
flight time total : 500
flight time type : 400
|Function||flight crew : single pilot|
|Qualification||other other : other|
|Experience||flight time total : 10|
|Anomaly||conflict : airborne less severe|
|Independent Detector||other other : unspecified|
other other : unspecified cockpit
|Resolutory Action||flight crew : took evasive action|
|Miss Distance||horizontal : 100|
vertical : 100
|Primary Problem||Flight Crew Human Performance|
|Air Traffic Incident||other|
After doing his run-up my student looked for traffic, and after he was sure that there were no aircraft on the traffic pattern he reported taking the active 35 to remain in the traffic pattern. He didn't hear nor see the X that reported 3 mi final for runway 35. When I saw the aircraft it was about 2 mi final and at this time my student had already started the takeoff roll. When the X was almost touching down, my student was lifting off, and at the time the X decided to go around my student was starting his climb. My student flew over the runway and the small transport X passed over my student at about 4500' from the beginning of the runway and close to him. As soon as my student landed he explained what happened and we tried to find the X pilot to tell him the we were sorry, but we had no success in finding him. It was my student's first solo. The problem arose because the X pilot flew a straight-in approach. My student was familiar with the FAA traffic pattern procedures and consequently didn't expect a straight-in entry. He made sure that there were no aircraft on the traffic pattern, but he didn't see the small transport that was in a 4 mi final straight-in approach.
Original NASA ASRS Text
Title: STUDENT PLT MAKING FIRST SOLO FLT DID NOT SEE SMT ON LONG STRAIGHT-IN FINAL AT UNCONTROLLED ARPT AND TOOK OFF. SMT OVERTOOK THE SMA PASSING IN CLOSE PROX.
Narrative: AFTER DOING HIS RUN-UP MY STUDENT LOOKED FOR TFC, AND AFTER HE WAS SURE THAT THERE WERE NO ACFT ON THE TFC PATTERN HE RPTED TAKING THE ACTIVE 35 TO REMAIN IN THE TFC PATTERN. HE DIDN'T HEAR NOR SEE THE X THAT RPTED 3 MI FINAL FOR RWY 35. WHEN I SAW THE ACFT IT WAS ABOUT 2 MI FINAL AND AT THIS TIME MY STUDENT HAD ALREADY STARTED THE TKOF ROLL. WHEN THE X WAS ALMOST TOUCHING DOWN, MY STUDENT WAS LIFTING OFF, AND AT THE TIME THE X DECIDED TO GO AROUND MY STUDENT WAS STARTING HIS CLB. MY STUDENT FLEW OVER THE RWY AND THE SMT X PASSED OVER MY STUDENT AT ABOUT 4500' FROM THE BEGINNING OF THE RWY AND CLOSE TO HIM. AS SOON AS MY STUDENT LANDED HE EXPLAINED WHAT HAPPENED AND WE TRIED TO FIND THE X PLT TO TELL HIM THE WE WERE SORRY, BUT WE HAD NO SUCCESS IN FINDING HIM. IT WAS MY STUDENT'S FIRST SOLO. THE PROB AROSE BECAUSE THE X PLT FLEW A STRAIGHT-IN APCH. MY STUDENT WAS FAMILIAR WITH THE FAA TFC PATTERN PROCS AND CONSEQUENTLY DIDN'T EXPECT A STRAIGHT-IN ENTRY. HE MADE SURE THAT THERE WERE NO ACFT ON THE TFC PATTERN, BUT HE DIDN'T SEE THE SMT THAT WAS IN A 4 MI FINAL STRAIGHT-IN APCH.
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.