 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Aircraft X, who had observed both aircraft Z, on its landing roll and aircraft Y on final, felt that ample space existed to takeoff between them. Aircraft Z did not clear the runway in a timely manner, forcing aircraft Y to execute a go around.
| Attributes | |
| ACN | 483428 |
| Time | |
| Date | 200008 |
| Day | Thu |
| Local Time Of Day | 1801 To 2400 |
| Place | |
| Locale Reference | airport : jyo.airport |
| State Reference | VA |
| Altitude | agl single value : 0 |
| Environment | |
| Flight Conditions | VMC |
| Light | Dusk |
| Aircraft 1 | |
| Operator | general aviation : personal |
| Make Model Name | PA-28 Cherokee Arrow IV |
| Operating Under FAR Part | Part 91 |
| Flight Phase | ground : position and hold |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Trinidad TB-21 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | landing : go around |
| Person 1 | |
| Affiliation | other |
| Function | flight crew : single pilot |
| Qualification | pilot : multi engine pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 6 flight time total : 2000 flight time type : 4 |
| ASRS Report | 483428 |
| Person 2 | |
| Function | flight crew : single pilot |
| Qualification | pilot : private |
| Events | |
| Anomaly | conflict : ground less severe incursion : runway non adherence : far |
| Independent Detector | other flight crewa |
| Resolutory Action | flight crew : executed go around none taken : anomaly accepted |
| Miss Distance | horizontal : 2400 |
| Supplementary | |
| Problem Areas | Flight Crew Human Performance |
| Primary Problem | Flight Crew Human Performance |
Narrative:
I had a clearance void time which was nearing as I was awaiting a number of landing aircraft. I had asked for one extension of the clearance void time, which was granted. There was an adequate gap between an aircraft touching down and the next landing aircraft. I took po on the runway, waiting for traffic to clear downfield. The traffic was slow to clear and the aircraft on the final went around. I believe there was adequate spacing available for the aircraft on final to continue and land. Even so, I didn't intend to be the cause of another aircraft having to execute a rejected landing even though safety was never compromised. Leesburg is a busy airport and at times has traffic that would seem to justify a tower there. Callback conversation with reporter revealed the following information: because of the cost of operating this aircraft. It made him do things that he has never done, such as being in a hurry and putting a lot of pressure on himself.
Original NASA ASRS Text
Title: ACFT X, WHO HAD OBSERVED BOTH ACFT Z, ON ITS LNDG ROLL AND ACFT Y ON FINAL, FELT THAT AMPLE SPACE EXISTED TO TKOF BETWEEN THEM. ACFT Z DID NOT CLR THE RWY IN A TIMELY MANNER, FORCING ACFT Y TO EXECUTE A GAR.
Narrative: I HAD A CLRNC VOID TIME WHICH WAS NEARING AS I WAS AWAITING A NUMBER OF LNDG ACFT. I HAD ASKED FOR ONE EXTENSION OF THE CLRNC VOID TIME, WHICH WAS GRANTED. THERE WAS AN ADEQUATE GAP BETWEEN AN ACFT TOUCHING DOWN AND THE NEXT LNDG ACFT. I TOOK PO ON THE RWY, WAITING FOR TFC TO CLR DOWNFIELD. THE TFC WAS SLOW TO CLR AND THE ACFT ON THE FINAL WENT AROUND. I BELIEVE THERE WAS ADEQUATE SPACING AVAILABLE FOR THE ACFT ON FINAL TO CONTINUE AND LAND. EVEN SO, I DIDN'T INTEND TO BE THE CAUSE OF ANOTHER ACFT HAVING TO EXECUTE A REJECTED LNDG EVEN THOUGH SAFETY WAS NEVER COMPROMISED. LEESBURG IS A BUSY ARPT AND AT TIMES HAS TFC THAT WOULD SEEM TO JUSTIFY A TOWER THERE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: BECAUSE OF THE COST OF OPERATING THIS ACFT. IT MADE HIM DO THINGS THAT HE HAS NEVER DONE, SUCH AS BEING IN A HURRY AND PUTTING A LOT OF PRESSURE ON HIMSELF.
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.