2025-10 · NASA ASRS report 2298907
Falcon 2000 flight crew reported airspeed and altitude instrument variations during climb. Flight crew continued to destination and landed.
Both PIC and SIC performed a walk around. As PIC; I removed the pitot covers and performed a visual inspection and found nothing out of the ordinary. SIC performed his own walk around and found nothing out of the ordinary as well. We performed our checks; fueled the aircraft and called for our clearance to ZZZ1. After starting engines; we called CTAF and advised we were taxiing to runway XX. SIC called clearance and received clearance for takeoff. As we were on takeoff roll; we both notice nothing out of the ordinary. As we achieve a positive rate of climb; I call for ''gear up''; SIC moves landing gear handle to the up position; and around 250-300' I start feeling some sort of buffeting from the airplane. I cross reference my instruments and notice that the airspeed; altitude and flight director indicators do not match what the airplane was actually doing. We follow our initial climb instructions of heading 360 and 2000'. As I make the left turn; the airplane's ''windshear'' alarm goes off. I instruct the SIC to let ATC know what was happening and he cleared us to climb to 4000'. Upon reaching 4000'; we follow vector instructions to the best of our ability. We are then vectored for a left 360 degree turn and request direct ZZZZZ for the RNAV XY. Approach then tried to vector us for runway XZ to which we mentioned we would land runway XY and requested 1700'. I kept cross referencing my instruments and all are reading different values. As all this was happening; we always had ZZZ1 in sight. As we were vectored to land runway XY; we told approach we were landing runway XY and we didn't have time to contact tower before safely landing the aircraft. Landing was secured and we were given instructions by tower to taxi to our hangar. Upon exiting our aircraft; our maintenance mechanic mentioned that the static ports were clogged for both PIC and SIC; he mentioned this happens with airflow which would make sense as this happened after taking off. Fortunately; we landed safely and were able to walk away with no injuries or aircraft damage of any kind.
Captain did the first walk around and was the one who removed covers from the plane. He found nothing out of the ordinary when he did his walk around. I found nothing either in my checks. We entered runway XX in ZZZ; initiated our takeoff roll and I was the PM; called 80kts; we crossed checked; V1 and VR; gear up and initially we had 2000ft and 360 heading as our takeoff clearance. As soon as I retracted gears PF engage autopilot and it started to pitch in a weird way as we were reading different airspeeds and altitudes. Both were erroneous and different from each other. We did let know approach about the issue we were having and we asked altitude and speed showing for them and he cleared us to climb to 4000ft. Captain requested me to ask approach to fly direct to ZZZZZ (FIX FOR RNAV XY) and over ZZZZZ approach asked for a left turn 270 heading vectoring is for runway XZ but we told them that we were landing on runway XY and requesting lower which they asked us to descend to 1700ft and then 1100ft. Important to mention that we always had the airport in sight. There was no time to contact tower and let them know we were landing in runway XY as we were with approach in short final. Landing was secured and then we taxied to parking and instructions were given by ZZZ1 tower. When we excited the aircraft; the maintenance noticed that the static ports were blocked on both sides. He mention that could have happened when airflow gets to the instruments after taking off which makes sense as everything happened after rotation.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.