37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1214366 |
Time | |
Date | 201410 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | MCO.Airport |
State Reference | FL |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | A320 |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | UAV - Unpiloted Aerial Vehicle |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Events | |
Anomaly | Conflict NMAC Inflight Event / Encounter Other / Unknown |
Narrative:
After takeoff; and just north of the orl VOR; we were given a turn to 270 degrees and a climb to and maintain 8000 feet. We leveled off at 8000 feet and stayed there for a minute or so. We had to wait until we were clear of [another] aircraft to climb higher.after we were clear; we were given a clearance to climb to 16000 feet. After passing 10000 feet; I performed my flow. I monitored to FMA; and saw that the climb speed increased from 250 knots to something around 290 knots. As we were accelerating; we hit a patch of rough air. I elected to select 250 knots for a temporary climb speed to climb a little quicker into smoother air.just as I pulled the speed selector to command the flight guidance to maintain 250 knots; something caught my eye. Orlando approach requested we switch to jacksonville center frequency at the same time. As the first officer began to read back the instructions; the same thing caught his eye; also. He stopped mid sentence.what we saw was a small remote controlled red aircraft with white and blue markings. I was fortunate to have pulled for open climb at 250 knots; because if I had let the aircraft accelerate; we may have been on an intersecting flight path. As it was; we only had 2-3 seconds to respond; but did not have to respond aggressively. We passed above the remote aircraft by 100-200 feet.all of this happened 17-18 northwest of mco at approximately 10;200-10;500 feet MSL.we immediately informed orlando departure control of what happened. He took the report; and then re instructed us to contact jacksonville center. We did; and the rest of the flight was uneventful.[I believe] all remote control aircraft owners need to register their aircraft so that a regulation book can be given to the owner of the craft.the remote controlled vehicle should be subject to the same rules as any other aircraft. If it flies into a B; C; or above 10000 feet in east airspace; it must have a transponder. There should also be a maximum distance and altitude a remote controlled vehicle can fly from its operator. Two miles high is too far for an operator to safely maneuver his craft safely.and finally; a written exam should be given to any operator of a class of remote controlled aircraft that can fly high enough; or fast enough to come into conflict with a traditional aircraft. If the test is not taken; or if it failed; the operator should be prohibited from flying his craft until the test is taken and passed.
Original NASA ASRS Text
Title: An A320 flight crew had a close encounter with a UAV they identified as a red; white and blue model aircraft operating above 10;000 FT; within the confines of and at or above the MCO Class B.
Narrative: After takeoff; and just north of the ORL VOR; we were given a turn to 270 degrees and a climb to and maintain 8000 feet. We leveled off at 8000 feet and stayed there for a minute or so. We had to wait until we were clear of [another] aircraft to climb higher.After we were clear; we were given a clearance to climb to 16000 feet. After passing 10000 feet; I performed my flow. I monitored to FMA; and saw that the climb speed increased from 250 knots to something around 290 knots. As we were accelerating; we hit a patch of rough air. I elected to select 250 knots for a temporary climb speed to climb a little quicker into smoother air.Just as I pulled the speed selector to command the flight guidance to maintain 250 knots; something caught my eye. Orlando approach requested we switch to Jacksonville Center frequency at the same time. As the First Officer began to read back the instructions; the same thing caught his eye; also. He stopped mid sentence.What we saw was a small remote controlled red aircraft with white and blue markings. I was fortunate to have pulled for open climb at 250 knots; because if I had let the aircraft accelerate; we may have been on an intersecting flight path. As it was; we only had 2-3 seconds to respond; but did not have to respond aggressively. We passed above the remote aircraft by 100-200 feet.All of this happened 17-18 northwest of MCO at approximately 10;200-10;500 feet MSL.We immediately informed Orlando Departure Control of what happened. He took the report; and then re instructed us to contact Jacksonville Center. We did; and the rest of the flight was uneventful.[I believe] all remote control aircraft owners need to register their aircraft so that a regulation book can be given to the owner of the craft.The remote controlled vehicle should be subject to the same rules as any other aircraft. If it flies into a B; C; or above 10000 feet in E airspace; it must have a transponder. There should also be a maximum distance and altitude a remote controlled vehicle can fly from its operator. Two miles high is too far for an operator to safely maneuver his craft safely.And finally; a written exam should be given to any operator of a class of remote controlled aircraft that can fly high enough; or fast enough to come into conflict with a traditional aircraft. If the test is not taken; or if it failed; the operator should be prohibited from flying his craft until the test is taken and passed.
Data retrieved from NASA's ASRS site 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.