37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 528121 |
Time | |
Date | 200110 |
Day | Sun |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : cez.airport |
State Reference | CO |
Altitude | agl bound lower : 0 agl bound upper : 350 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tower : mlb.tower |
Operator | common carrier : air carrier |
Make Model Name | Beech 1900 |
Operating Under FAR Part | Part 135 |
Flight Phase | descent : approach |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air taxi |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Operating Under FAR Part | Part 135 |
Flight Phase | descent : approach |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air taxi |
Function | flight crew : captain oversight : pic |
Qualification | pilot : cfi pilot : commercial pilot : instrument pilot : multi engine pilot : atp |
Experience | flight time last 90 days : 300 flight time total : 1800 flight time type : 1100 |
ASRS Report | 528121 |
Person 2 | |
Affiliation | company : air taxi |
Function | flight crew : first officer |
Events | |
Anomaly | conflict : ground critical incursion : runway non adherence : far non adherence : published procedure non adherence : required legal separation other anomaly other other spatial deviation |
Independent Detector | other flight crewa other flight crewb |
Resolutory Action | flight crew : executed go around flight crew : took evasive action |
Consequence | other |
Miss Distance | horizontal : 0 vertical : 500 |
Supplementary | |
Problem Areas | Airport Company Flight Crew Human Performance |
Primary Problem | Flight Crew Human Performance |
Situations | |
Airport | procedure or policy : cez.airport |
Narrative:
First officer's leg. I had just completed the final landing checklist that is called for at 500 ft AGL, when, simultaneously, I looked up and saw something on the runway. A cessna holding short advised us that an ultra light was doing a touch and go on the same runway 21. We initiated a go around, and proceeded back in the traffic pattern for an uneventful landing on runway 21. The ultra light had no radio or transponder so we had virtually no way of identifying his presence. During the traffic pattern back around, I was very thankful to have the help of the cessna and unicom. In identifying where he was. Later, while parked at our terminal, I observed, incredulously, what I believed as the ultra light cutting off the cessna after flying a low pattern. I never verified this with the cessna however, this was the same cessna that had previously warned us of the ultra light's presence-he was doing full-stop taxi back's using runway 21. Then, while departing cortez on flight XXXX 15-20 mins later, we finished our checklists and called departing runway 21 on CTAF. At that point unicom told us to hold short and that the same ultra light was taxiing for what looked like a departure off runway 3, and that 'he doesn't look like he's stopping.' we did hold short. Runway 3 was not the runway the established traffic was using winds were calm-light variable. I gained some information from the local FBO (unicom) apparently this man operates a company on the field. I do not know his name or the company's purpose but it appeared that he was taking people up for rides and sight seeing tours the first officer reported that she saw a small child on board after he landed after cutting off the cessna (unverified.) I think it would be great fun and experience to fly an ultra light-but this man appeared particularly reckless-and was in clear violation of the aim, far 103.13, and possibly far 103.17. In speaking with only a few people I did find one other pilot who has had problems with ultra lights at cortez. That's good odds that there are more. Of course, I am worried about my crew and passenger's safety, but I am also worried about his. If this man is running a company on the field then I am even stronger in my belief to either move him off the field or create a dirt strip so he's not occupying the same runway as us. In either case he should gain more knowledge of flight rules or be shut down-or moved completely off the airspace. Callback conversation with reporter revealed the following information: the reporter turned in a report to his chief pilot but does not know what his company plans to do about this situation. He had not advised the FAA or the local FSDO about the incident. He is not aware if the ultra light company has more than one aircraft or what their operation consists of so far as operating hours or number of pilots. Reporter had been into cez about 15 times, had seen the ultralight but never had previous encounter with same.
Original NASA ASRS Text
Title: A BE-1900D PIC RPT ON THE ALLEGED ERRATIC OP OF AN ULTRALIGHT THAT CREATED MULTIPLE TFC PROBS AT CEZ, CO.
Narrative: FO'S LEG. I HAD JUST COMPLETED THE FINAL LNDG CHKLIST THAT IS CALLED FOR AT 500 FT AGL, WHEN, SIMULTANEOUSLY, I LOOKED UP AND SAW SOMETHING ON THE RWY. A CESSNA HOLDING SHORT ADVISED US THAT AN ULTRA LIGHT WAS DOING A TOUCH AND GO ON THE SAME RWY 21. WE INITIATED A GAR, AND PROCEEDED BACK IN THE TFC PATTERN FOR AN UNEVENTFUL LNDG ON RWY 21. THE ULTRA LIGHT HAD NO RADIO OR TRANSPONDER SO WE HAD VIRTUALLY NO WAY OF IDENTIFYING HIS PRESENCE. DURING THE TFC PATTERN BACK AROUND, I WAS VERY THANKFUL TO HAVE THE HELP OF THE CESSNA AND UNICOM. IN IDENTIFYING WHERE HE WAS. LATER, WHILE PARKED AT OUR TERMINAL, I OBSERVED, INCREDULOUSLY, WHAT I BELIEVED AS THE ULTRA LIGHT CUTTING OFF THE CESSNA AFTER FLYING A LOW PATTERN. I NEVER VERIFIED THIS WITH THE CESSNA HOWEVER, THIS WAS THE SAME CESSNA THAT HAD PREVIOUSLY WARNED US OF THE ULTRA LIGHT'S PRESENCE-HE WAS DOING FULL-STOP TAXI BACK'S USING RWY 21. THEN, WHILE DEPARTING CORTEZ ON FLT XXXX 15-20 MINS LATER, WE FINISHED OUR CHKLISTS AND CALLED DEPARTING RWY 21 ON CTAF. AT THAT POINT UNICOM TOLD US TO HOLD SHORT AND THAT THE SAME ULTRA LIGHT WAS TAXIING FOR WHAT LOOKED LIKE A DEPARTURE OFF RWY 3, AND THAT 'HE DOESN'T LOOK LIKE HE'S STOPPING.' WE DID HOLD SHORT. RWY 3 WAS NOT THE RWY THE ESTABLISHED TFC WAS USING WINDS WERE CALM-LIGHT VARIABLE. I GAINED SOME INFO FROM THE LOCAL FBO (UNICOM) APPARENTLY THIS MAN OPERATES A COMPANY ON THE FIELD. I DO NOT KNOW HIS NAME OR THE COMPANY'S PURPOSE BUT IT APPEARED THAT HE WAS TAKING PEOPLE UP FOR RIDES AND SIGHT SEEING TOURS THE FO RPTED THAT SHE SAW A SMALL CHILD ON BOARD AFTER HE LANDED AFTER CUTTING OFF THE CESSNA (UNVERIFIED.) I THINK IT WOULD BE GREAT FUN AND EXPERIENCE TO FLY AN ULTRA LIGHT-BUT THIS MAN APPEARED PARTICULARLY RECKLESS-AND WAS IN CLR VIOLATION OF THE AIM, FAR 103.13, AND POSSIBLY FAR 103.17. IN SPEAKING WITH ONLY A FEW PEOPLE I DID FIND ONE OTHER PILOT WHO HAS HAD PROBS WITH ULTRA LIGHTS AT CORTEZ. THAT'S GOOD ODDS THAT THERE ARE MORE. OF COURSE, I AM WORRIED ABOUT MY CREW AND PAX'S SAFETY, BUT I AM ALSO WORRIED ABOUT HIS. IF THIS MAN IS RUNNING A COMPANY ON THE FIELD THEN I AM EVEN STRONGER IN MY BELIEF TO EITHER MOVE HIM OFF THE FIELD OR CREATE A DIRT STRIP SO HE'S NOT OCCUPYING THE SAME RWY AS US. IN EITHER CASE HE SHOULD GAIN MORE KNOWLEDGE OF FLT RULES OR BE SHUT DOWN-OR MOVED COMPLETELY OFF THE AIRSPACE. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR TURNED IN A RPT TO HIS CHIEF PLT BUT DOES NOT KNOW WHAT HIS COMPANY PLANS TO DO ABOUT THIS SIT. HE HAD NOT ADVISED THE FAA OR THE LOCAL FSDO ABOUT THE INCIDENT. HE IS NOT AWARE IF THE ULTRA LIGHT COMPANY HAS MORE THAN ONE ACFT OR WHAT THEIR OP CONSISTS OF SO FAR AS OPERATING HRS OR NUMBER OF PLTS. RPTR HAD BEEN INTO CEZ ABOUT 15 TIMES, HAD SEEN THE ULTRALIGHT BUT NEVER HAD PREVIOUS ENCOUNTER WITH SAME.
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.