elihoole/asrs-aviation-reports huggingface dataset:
Date: 201212
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Light Sport Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Takeoff / Launch
Airspace: Class C ZZZ
ATC / advisory: Tower ZZZ
Aircraft component: Aeroplane Flight Control
Component problem: Failed
Reporter organization: Personal
Reporter function: Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Multiengine; Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Critical; Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Aircraft Aircraft Damaged; General Evacuated
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: The airport was reporting VFR with calm winds. I performed a preflight check; then taxied over to the fuel pumps and filled up with 12.10 gallons. Upon completion I performed all preflight and before takeoff checklists. The Tower cleared me for takeoff. After a normal take-off run with a speed of about 75 to 80 knots I rotated and was experiencing a normal climb until reaching approximately 50 to 75 feet above the ground whereupon the aircraft suddenly pitched left and was unresponsive to control inputs. Just before impact; I tried to flare and reduced the throttle. Once the airplane came to a rest; we slid open the canopy and before stepping out shut off all fuel and electrics. Fire and EMS personnel were there five to 10 minutes later.




Synopsis: On a clear; calm day the pilot of a Globe Swift suffered loss of flight control shortly after lift off and the airplane banked to the left and impacted the ground.  The pilot exited the aircraft and was uninjured.
Date: 202109
Local time of day: 1201-1800
Location: S72.Airport, ID
Flight conditions: VMC
Light: Daylight
Aircraft: Small Aircraft
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Landing
Airspace: Class G S72
ATC / advisory: UNICOM S72
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Flight Engineer; Flight Crew Multiengine; Flight Crew Instrument
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Calm clear no wind day. Lots of calls from Coeur D'Alene. Conflicting traffic on climbout.




Synopsis: GA pilot reported an NMAC at S72 non-towered airport.
Date: 202001
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: IMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Airspace: Class B ZZZ
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Human factors: Other / Unknown
Anomaly: Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor
Detector: Person Flight Attendant; Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: Odors are subjective in nature. Communication between the cabin and flight deck needs to be less subjective. A better description of an odor; the location; duration and intensity would be more helpful.




Synopsis: A320 First Officer reported the need for more definitive information regarding the identification of odors on aircraft.
Date: 201505
Flight conditions: VMC
Aircraft: A319
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Aircraft component: Electronic Flt Bag (EFB)
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Aircraft Equipment Problem Less Severe
Detector: Person Flight Crew
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Aircraft; Human Factors
Primary problem: Ambiguous

Narrative: During the flight both Captain and First Officer were locked out of their iPads due to password issues! Without either iPad being accessible we had no Flight Manual; Bulletins; FOM etc.. I am sure this has happened before and will happen again. I literally felt unsafe without being able to access to my iPad. This flight had a hydraulic problem that required lots of resource management.




Synopsis: A319 Captain and First Officer both experience password issues and are unable to access their iPads in flight.
Date: 201911
Local time of day: 0601-1200
Flight conditions: VMC
Light: Daylight
Aircraft: Regional Jet 900 (CRJ900)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Climb
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Human factors: Situational Awareness; Fatigue
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: On the departure from ZZZ to GDL ATC advised us to correct course immediately to avoid terrain; at this point we were well clear of all terrain in sight though admittedly South Mountain did look a bit closer than usual but I chalked that up to our heavy takeoff weight which was within limits but just. ATC then gave us a few more vectors and eventually direct ZZZZZ way point. ATC then issued us instructions to call tower for possible pilot deviation. As we checked over the FMS we realized that we had neglected to select the departure Runway XXL for the departure which put us on the wrong course. This is not an unfamiliar airport for us and we did run all checklists which means we both missed it three times.This may be a case of seeing what we want to see. I looked and saw the departure was in the box just like it was supposed to be; and only after being advised of impending doom did we really look. Fortunately; we were not unsafely close to terrain or traffic this time; but the potential it could have been is real.




Synopsis: Flight Crew flying CRJ-900 aircraft flew wrong departure procedure.
Date: 201508
Local time of day: 1201-1800
Location: PAO.Airport, CA
Flight conditions: VMC
Weather elements / visibility: wind gusts; 10
Light: Daylight
Aircraft: Cessna Stationair/Turbo Stationair 6
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Passenger
Flight phase: Landing
Airspace: Class D X
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Private
Human factors: Troubleshooting; Training / Qualification
Anomaly: Ground Event / Encounter Ground Strike - Aircraft
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Provided Assistance; Aircraft Aircraft Damaged; Flight Crew Requested ATC Assistance / Clarification; General Maintenance Action
Contributing factors: Weather
Primary problem: Weather

Narrative: At landing roll-out; airplane bounced multiple times on runway with divergent attitude. Front landing gear fractured followed by propeller ground strike. The aircraft landed safely but lost steering ability on the ground; and subsequently had to be towed off the runway. No personal injury or other property damage.




Synopsis: A Private Pilot bounced a C-206 multiple times on landing. Winds were reported as gusty. The front landing gear fractured and the propeller struck the ground.  The aircraft had to be towed off the runway.
Date: 201702
Local time of day: 0601-1200
Location: VNC.Airport, FL
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 152
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Training
Flight phase: Landing
Airspace: Class E VNC
ATC / advisory: CTAF VNC
Second aircraft: SR22
Reporter organization: Personal
Reporter function: Instructor
Reporter qualification: Flight Crew Flight Instructor
Anomaly: Conflict NMAC
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Human Factors
Primary problem: Human Factors

Narrative: We were doing touch and go runway 31 at VNC; about midfield downwind; when a Cirrus (SR-22) came from our left wing entered direct downwind 31 at VNC. I had to take evasive action sharp bank to the right to not collide with him.




Synopsis: C-152 instructor reported a near mid-air with an SR-22 while on downwind for Runway 31 at VNC.
Date: 201904
Local time of day: 0601-1200
Location: FUL.Airport, CA
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Cessna 170
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Cruise
Airspace: Class D FUL
ATC / advisory: Tower FUL
Second aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Reporter organization: Personal
Reporter function: Single Pilot
Reporter qualification: Flight Crew Private; Flight Crew Instrument
Human factors: Distraction; Time Pressure; Situational Awareness
Anomaly: Airspace Violation All Types; Conflict NMAC; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew Took Evasive Action
Contributing factors: Airspace Structure; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: While flying to ZZZ; the FUL Tower said to either climb or descend to avoid a medfly aircraft at my then altitude of 2;000 feet MSL. I would soon be passing over hills so I chose to climb to avoid the medfly aircraft. I leveled off for a few seconds at 2;400 MSL as I saw the medfly below and reported it to FUL Tower and descended.I noticed that I was under the south east corner of the LAX class B. I decided to report this as I usually stay at 2;000 MSL in this area and I do not know what the computers said my altitude was. If there was any intrusion into class B it was inadvertent due to towers request I avoid the other aircraft and my eyes were out the window looking for the other aircraft. I had my ForeFlight display on my mini but was looking for the actual aircraft.




Synopsis: C170 pilot reported possible Class B violation while avoiding another aircraft.
Date: 201605
Local time of day: 1201-1800
Location: ZZZ.ARTCC, US
Aircraft: Citationjet (C525/C526) - CJ I / II / III / IV
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Training / Qualification
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Air Traffic Control Provided Assistance; Air Traffic Control Separated Traffic
Contributing factors: Human Factors; Manuals; Airspace Structure; Procedure
Primary problem: Manuals

Narrative: Neighboring sector handed me off Aircraft X with Flight Level 330 descending Flight Level 240 in the data block very near my boundary. My boundary is 80 miles from Aircraft X's destination. I usually get pointouts on these inbounds. Aircraft X had been vectored to parallel an overflight at 31;000 feet. Their sector was fairly busy and mine had slowed down just recently from a very busy period. I got a call about 1 minute flying time from my boundary that Aircraft X was my control with adjacent underlying sectors. This call was pretty useless because of the now 45 seconds flying time to my boundary; the plane's altitude; and the fact that the pilot didn't even call until my boundary anyway.The pilot calls and says 'descending to Flight Level 310' when the data block showed Flight Level 240. Still on a northeast vector to parallel the traffic I told the pilot to descend to 24;000 feet and 'set up for crossing 30 miles west of destination at 9;000 feet' because the landing runway is essentially a straight-in approach from the west. Pilot acknowledges but STILL floats his plane down. I call sector underlying me; and give them control. That sector has to vector the plane quite a bit more for appropriate altitude loss.I hear talk from the area which we received this plane that this pilot 'does this all the time.' Well for one; pilots only do what we allow them to and number two; their controller did not meet our facility SOP.Especially during busier times; allowing pilots to 'hang it up' or some such is unacceptable. I would ensure that controllers stick fairly strictly to the SOP REGARDLESS of pilot whining.




Synopsis: A Center Controller received a handoff on an aircraft at an altitude not in compliance with the facility SOP manual.
Date: 202009
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: Haze / Smoke
Light: Daylight
Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Descent
Airspace: Class E ZZZ
Reporter organization: Personal
Reporter function: Single Pilot; Pilot Flying
Reporter qualification: Flight Crew Instrument; Flight Crew Private
Human factors: Situational Awareness
Anomaly: Airspace Violation All Types; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Took Evasive Action
Contributing factors: Procedure; Environment - Non Weather Related; Human Factors
Primary problem: Ambiguous

Narrative: During a personal flight; I observed smoke associated with a fire; and lots of aerial traffic swarming around that area; according to ADS-B.  The location of the fire was approximately X NM NW of ZZZ1; while I was flying a line between ZZZ and ZZZ1.  My EFB software was not showing a TFR in this location; but did show other TFR's.  The activity suggested there was a TFR; so I adjusted my position to be further east.  Checking the FAA TFR site on my phone upon landing ZZZ1 showed there was a TFR created since my preflight briefing at home; but before entering the area in the flight.  I believe I remained clear; but very close.Contributing factors:TFR was created in that window of time between briefing and flight. In-flight data is relied on for these updates; but the TFR did not post in time. ATC has been difficult to get flight following since Pandemic made them busier; so I stopped trying for short flights.Discovery was recognizing the situation; and corrective action was making room for fire fighting.




Synopsis: Pilot reported flying nearby an area of smoke and was unable to find an associated TFR. After the flight; pilot confirmed a TFR was active but did not post in time on EFB software.
Date: 201604
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Daylight
Aircraft: Light Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Landing
ATC / advisory: CTAF ZZZ
Aircraft component: Parking Brake
Component problem: Malfunctioning
Reporter organization: Fractional
Reporter function: Pilot Not Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Troubleshooting; Confusion
Second reporter function: Pilot Flying; First Officer
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: General Evacuated
Contributing factors: Aircraft; Human Factors; Procedure
Primary problem: Human Factors

Narrative: Taxi out was normal to the Runway. We held short of the Runway and then were cleared for takeoff. I turned off the parking brake and taxied into position for takeoff under normal power settings.  We transferred controls and did a semi static takeoff roll. Upon takeoff roll after passing 90kts I noticed the aircraft seemed slow to accelerate to V1. Everything up to 90 kts was normal. V1 100; V2 104 but it was too late to abort at that point. We had passed V1 and approached V2. We rotated and the aircraft picked up speed quickly and everything seemed normal. We retracted the gear and the flaps at Flap Retraction Altitude (FRA). At that point we both mentioned it seemed as if the brakes were on. I looked at the parking brake and found it to be out an inch. We immediately talked about dropping the gear for cooling purposes. We agreed to do that but also continued the departure. After a little more than a minute we retracted the gear again. We had no indication of anything being wrong so we continued to our destination. Remainder of flight was normal until about 500 feet after touchdown the braking seemed harder than normal as if the brakes were being fully depressed. The anti skid was trying to assist with the braking with no effect. We never received an anti skid light either. Pilot Flying (PF) mentioned he wasn't using the brakes at all but the plane was slowing quickly. Thrust reversers (TRs) were deployed momentarily and then retracted. Speedbrakes were deployed upon landing. As aircraft came to a stop we preformed our shutdown procedures and evacuation of the passengers on the runway and declared the airport closed.


Second narrative: [Report narrative contained no additional information.]


Synopsis: A Cessna Citation crew may have left parking brake set during takeoff roll. The aircraft evacuated upon landing due to suspected parking brake application.
Date: 201511
Local time of day: 1201-1800
Location: ZZZ.TRACON, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Daylight
Aircraft: Learjet 35
Operator: Air Taxi
Operating under: Part 135
Flight plan: IFR
Mission: Passenger
Flight phase: Descent
Airspace: Class E ZZZ
ATC / advisory: TRACON ZZZ
Reporter organization: Air Taxi
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Instrument; Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Multiengine
Second reporter function: First Officer; Pilot Not Flying
Anomaly: ATC Issue All Types; Deviation - Altitude Overshoot; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Took Evasive Action
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: Approach Control issued a descent and heading. We read back 2;000 and continued. Shortly thereafter we were switched to another controller and we replied with the heading and 2;000 feet again. Sometime later as we descended we were asked what our altitude was and we replied 2;600. We were told to climb to 3;000 which we did. Then were told that they usually issued 4;000 in our position. Weather was clear and although I thought the altitude was a little low we had the field in site from more than 20 miles out.A conversation with ATC revealed they had only issued 6;000 feet. and they twice failed to catch it on read back. I would hope that ATC would catch a questionable read back and a lower altitude than normal much quicker.


Second narrative: We were issued a descent down to what we had thought was two thousand feet. I read back to the controller that we were descending down to two thousand feet and the controller didn't say anything about it. The controller then came back and gave us another vector and I said again the heading in which he told me and said we were descending to two thousand. As we got to around 2;700-2;600 the controller came back and said we should have been at 4;000 and then told us to climb to 3;000 for the visual approach.


Synopsis: The flight crew of a LR35 descended below the ATC cleared altitude due to a communication breakdown during issuance and read back.
Date: 201308
Local time of day: 0601-1200
Location: ZZZ.ARTCC, US
Weather elements / visibility: Rain; 5
Light: Daylight
Aircraft: SR22
Operator: Personal
Operating under: Part 91
Flight plan: IFR
Mission: Ferry / Re-Positioning
Flight phase: Cruise
Airspace: Class C ZZZ
ATC / advisory: Center ZZZ
Aircraft component: AC Generator/Alternator
Component problem: Failed
Reporter organization: Personal
Reporter function: Single Pilot; Captain
Reporter qualification: Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Overcame Equipment Problem; General Declared Emergency
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: Flying IFR [at] 11;000 FT. ALT Number 1 failed. I notified ATC. AMP drain was 6 AMPS. I ran through the checklist for ALT 1 failure per the Cirrus manual twice. ALT Number 1 would not reset. I reduced the electrical load as much as I could include turning down the brightness on the PFD and MFD. I was over water when my MFD failed. OAT was +2 C; and I couldn't use pitot heat because of the additional electrical drain. I could also tell that my comms were intermittent. At that point I declared an emergency and requested direct to HPN. (The original routing was an arrival which would have added time). ATC was helpful and gave me direct. ATC gave me a descent which got me in warmer conditions and gave me vectors to the field. At about 4;000 FT. I broke out of the clouds and as I crossed the coast; I had the field in sight. ATC cleared me for the visual. My comms kept dropping out and I requested a change to Tower. That was approved; and my communications with the Tower was broken at best. They cleared me to land; which I did without incident; but with no flaps. After landing; I taxied to the ramp and was greeted by the fire truck and filled in a form noting that I had had an electrical failure. During the declaration process; ATC wanted to know A/C type; SOB and fuel in pounds. I was a bit shaken at that point and incorrectly stated 60 pounds; when it was 60 gals. The airplane is now in for maintenance.




Synopsis: SR22 pilot reported he lost the Number 1 alternator. Reporter declared an emergency and landed safely.