elihoole/asrs-aviation-reports huggingface dataset:
Date: 201211
Location: ZZZ.Airport, US
Aircraft: Citation Excel (C560XL)
Operator: Fractional
Operating under: Part 91
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft Terrain Warning
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Aircraft; Environment - Non Weather Related
Primary problem: Ambiguous

Narrative: While descending through 2;600 FT on a 3-5 mile left base the EGPWS commanded 'obstacle; PULL UP!' Alert went away as soon as the descent rate was arrested. Crew elected to abandon approach and circle back to land. No further alerts were received and landing was uneventful. Passengers did not seem to notice and were unfazed by the event.




Synopsis: A C560XL flight crew responded appropriately to an EGPWS obstacle warning while on a left base to their destination.
Date: 202201
Aircraft: Any Unknown or Unlisted Aircraft Manufacturer
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Dispatch
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Equipment / Tooling; Software and Automation
Primary problem: Ambiguous

Narrative: Possible confusion in planning and filing due to cut over to 5G.




Synopsis: Air carrier Dispatcher reported a possible mistake while processing a flight's documents during the 5G crossover period.
Date: 201507
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Light: Dusk
Aircraft: Medium Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction
Second reporter function: Pilot Not Flying; First Officer
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: Taxi
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: We were given clearance from ZZZ Tower to 'taxi into and hold; Runway 25R; keep proceeding Company aircraft in sight.' After having lined up; stopped; and holding on Runway 25R; I kept my eyes on the proceeding Company aircraft taking off while reaching down to set the parking brake and inadvertently moved number one start lever off the START position causing number one engine to roll back. Realizing what I had done; I immediately placed the number one start lever to CUTOFF and directed First Officer to request Tower that we needed to clear the runway; and he immediately made that request. Just after that transmission; ZZZ Tower issued takeoff clearance but we declined the takeoff clearance and again requested that we needed to clear off. We were given taxi clearance and we cleared the runway at Taxiway B1 and no aircrafts were in the vicinity. Tower asked if we needed assistance and we declined. We subsequently cooled and cleared the affected engine and accomplished engine start; made a PA to the Passengers; waited for Ops Limit of two minutes; and accomplished Before Taxi and Before Takeoff Checklists and then took off. All engine parameters were normal.


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


Synopsis: The Captain inadvertently selected the #1 start lever instead of the parking brake after lining up on the runway while focused on the instructions to keep the preceding company aircraft in sight.
Date: 201812
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Light: Daylight
Aircraft: Regional Jet 700 ER/LR (CRJ700)
Operator: Air Carrier
Operating under: Part 121
Flight phase: Parked
Reporter organization: Air Carrier
Reporter function: Technician
Reporter qualification: Maintenance Airframe; Maintenance Powerplant
Human factors: Communication Breakdown; Confusion; Workload; Situational Awareness; Training / Qualification
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Object
Detector: Person Maintenance
When detected: Taxi
Result: Aircraft Aircraft Damaged; General Maintenance Action
Contributing factors: Procedure; Human Factors; Company Policy; Staffing
Primary problem: Human Factors

Narrative: I was trying to be helpful staying on overtime to help dayshift wing walk Aircraft X into the hanger because they didn't have enough people to do so. The plane arrives back from the gate to the hanger. We hook up the tow bar with tug to start moving the aircraft inside. Me and Person 2 were the only wing walkers and Person 3 was on the tug. Person 3 didn't have a tail walker. So he starts moving the plane inside the hanger nose in. Well; as Person 3 is moving the plane he angles the plane to me so he clears Person 2 side because the hanger doors were not opened all the way. After Person 3 clears Person 2 wing tip on his side; he cuts the wheel so the wing tip on my side would clear. Well when he cut the wheel; he could no longer see me and if I went in his line of sight I would no longer be able to see if the wing tip clears; so Person 2 was walking to my side so he could tell how much clearance we have and that's when I crossed my arms and said cut it stop because the wing tip was going to hit the hanger door and Person 3 kept moving with the tug and hit the hanger door with the right hand wing tip and Person 2 even seen me cross my arms and he didn't say anything to the tug driver.The tug driver should have had a tail walker before tugging the aircraft and the hanger doors should have been more open but Person 3 said it was enough room  also Person 2should have told Person 3 the tug drivers I had my arms cross to stop.




Synopsis: During tow of CRJ-200 aircraft into hanger; wing tip contacted hanger door.
Date: 201307
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: B767 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Takeoff / Launch
ATC / advisory: Tower ZZZ
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Other / Unknown
Anomaly: Inflight Event / Encounter Loss Of Aircraft Control
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Regained Aircraft Control
Contributing factors: Weather; Human Factors; Aircraft
Primary problem: Ambiguous

Narrative: This was a ferry flight in a 767 with the winglets. Weather VMC and direct crosswind of 15 knots. Some discussion with load planning on taxi out as they seemed to be unfamiliar with planning numbers for a ferry flight. Trim was 1.8 which is quite a bit further forward than normal. Normal start of takeoff roll with a slight input forward stick and slight aileron into the wind. Speeds were 118 124 136 for very light weight. First Officer called V1 and at this time the aircraft lifted itself into the air without any input from me and well below rotate speed. Started pushing forward on yoke to lower nose and aircraft began to drift/skid toward the downwind side of the runway. Would not climb; controls extremely mushy and as I pushed the nose further down it settled back on the mains back on the runway. Speed began to build and gently flew plane off the runway with still nose down elevator input. Remainder of climb uneventful and upon leveling off; trim setting on autopilot was in the 3.5 to 4.0 range. Sent a request to inspect aircraft and cargo holds upon arrival. They said all cargo bays were empty. As I looked around the aircraft I noticed that the nose strut was fully extended and the aircraft was slightly tipped toward the rear. This after a normal landing with autobrakes 2 and a fairly rapid deceleration. In my entire career this is the closest I have ever come to loosing control of an aircraft which could have resulted in destroying the aircraft. I just barely saved this one.




Synopsis: B767 Captain experiences an early lift off on a ferry flight as the First Officer is calling V1. The aircraft touches down again before finally becoming airborne and continuing to destination.
Date: 201303
Local time of day: 1201-1800
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Aircraft: MD-83
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Tower ZZZ
Second aircraft: Cirrus Aircraft Undifferentiated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Distraction; Situational Awareness; Communication Breakdown
Second reporter function: First Officer; Pilot Not Flying
Anomaly: Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Clearance; Ground Incursion Runway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi

Narrative: We were cleared to taxi via Charlie onto Runway XX and hold short of Runway YY. We taxied onto Runway XX took a left and I said clear left after I saw company taxi across Runway YY; and my co-pilot said 'watch out for the guy on the right!' I saw a Cirrus approaching Runway YY and slammed on the brakes. I heard my Lead Flight Attendant let out a yelp and lifted off the brakes after I heard her scream and crash into the flight deck door.As I let off the brakes the Cirrus was 100 FT above us and well beyond the nose of our airplane. I mistakenly crossed over onto Runway YY. I saw no more danger so I continued to cross so I would not be in the middle of the runway. We stopped after that and contacted ground who told us to write down a phone number and contact Tower at our destination. We landed in [the airport] and I made the phone call immediately to Tower. I talked to a very nice gentlemen who said he wished he could handle this in house but it he would have to pass it along to regional office and then to the FSDO. I told him I was in the wrong and accept full responsibility. He said 'unfortunately these things happen.' I then contacted both chief pilots.


Second narrative: I believe both the Captain and I had become accustomed to having the same taxi instructions for the past five days in a row. To the best of my knowledge; we are routinely cleared for that taxi route without holding short at Runway YY. I think that we got too relaxed in the comfortable environment and failed to verify with each other our complete taxi instructions at every intersection. Slowing down and verbal verification between the Captain and First Officer of runway crossing/hold short instructions are undoubtedly key. Also; to always review written down taxi instructions at each and every runway or taxiway intersection prior to entering that runway/taxiway.


Synopsis: While taxiing on intersecting runways for takeoff; an MD-83 flight crew experienced a close encounter with a Cirrus on final to a runway they had been cleared to hold short of. Fatigue induced complacency and familiarity were cited as contributing factors.
Date: 201704
Local time of day: 0001-0600
Location: ZTL.ARTCC, GA
Flight conditions: Marginal
Light: Night
Aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Operator: Air Taxi
Operating under: Part 135
Flight plan: VFR
Mission: Passenger
Flight phase: Final Approach
Airspace: Class E AGS
ATC / advisory: Center ZTL
Second aircraft: Commercial Fixed Wing
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control; Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach; Flight Crew Requested ATC Assistance / Clarification
Contributing factors: Procedure; Human Factors; Chart Or Publication; Weather
Primary problem: Human Factors

Narrative: Operating on night configuration and I had assumed control of TRACON's airspace. Aircraft X and Aircraft Y were tied looking for approach clearances into AGS. Aircraft Y had already been assigned direct field and descent clearance so I gave Aircraft X holding instructions to wait for Aircraft Y's cancellation/down time. Aircraft X's pilot seemed irritated that he had to hold for a clearance into AGS at midnight.I informed the pilot that the Center can only provide services one in/one out. I issued Aircraft X holding instructions. A short time later Aircraft X's pilot inquired if could he cancel his IFR flight plan and proceed VFR into AGS. I informed him that he could at which point Aircraft X cancelled his IFR flight plan and continued his flight VFR. Aircraft Y was proceeding on a Visual Approach clearance into AGS. Sometime later Aircraft Y reported weather conditions did not permit him to go in visually and he had already began his turn away from AGS and started a climb out towards the ILS. I issued Aircraft Y a clearance direct to the initial approach fix for a procedure turn inbound. Aircraft Y later reported that an aircraft had descended through his altitude in close proximity going into AGS. He was concerned the pilot of that aircraft could not see him. I informed him it was most likely the aircraft which had cancelled IFR and was proceeding VFR into the field. Aircraft Y continued on to perform the ILS approach. Before leaving he voiced his concern that there were definitely IFR condition at AGS.




Synopsis: ZTL Center Controller reported an IFR aircraft going missed from a visual approach had a VFR aircraft descend through his altitude in IMC.
Date: 201911
Location: ZZZ.Airport, US
Weather elements / visibility: Rain
Light: Night
Aircraft: B757 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
Reporter organization: Air Carrier
Reporter function: Pilot Flying; Captain
Reporter qualification: Flight Crew Multiengine; Flight Crew Instrument; Flight Crew Air Transport Pilot (ATP)
Human factors: Communication Breakdown
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Ground Event / Encounter Other / Unknown
Detector: Person Flight Crew
When detected: Aircraft In Service At Gate
Result: Flight Crew Overcame Equipment Problem
Contributing factors: Equipment / Tooling
Primary problem: Equipment / Tooling

Narrative: Prior to pushback from the gate; at night and in the rain; the pushback crew had a hard time hearing me on the headset and repeatedly asked me to speak up. They came through to me intermittently and then just before push; communications seemed normal. As we were pushing back parallel to the gate; ramp requested we push deeper to give another aircraft room to push. I passed along this info to the pushback crew and received no response. The aircraft was stopped in the normal push position (not the newly requested position) and I could tell that the push crew was trying to communicate with me but nothing was coming through. Again; I said (loudly) to push us further back. I received no verbal acknowledgment; but we did eventually push further back. After we stopped I received no communication to set brakes. I could see confusion on the ramp and someone gave me the 'stop' sign. I set the brakes; then the tow bar was disconnected and someone ran out to show me the bypass pin as the tug pulled away. In the meantime; we tried to contact Operations to have a new headset brought out to the push crew; but by then we were understanding each other with hand signals. The difficulty was that it was raining and the pushback crew was standing to the side of the cockpit where we have no way to clear the windshield and I could barely see them through the window due to the rain.




Synopsis: B767 Captain reported that a faulty headset resulted in a communication breakdown with the ground crew during pushback.
Date: 201310
Local time of day: 1801-2400
Location: ZZZ.Airport, US
Flight conditions: VMC
Weather elements / visibility: 10
Light: Night
Aircraft: Small Aircraft; Low Wing; 1 Eng; Fixed Gear
Operator: Personal
Operating under: Part 91
Flight plan: None
Mission: Personal
Flight phase: Final Approach
Airspace: Class G ZZZ
ATC / advisory: CTAF ZZZ
Reporter organization: Personal
Reporter function: Pilot Flying; Single Pilot
Reporter qualification: Flight Crew Commercial; Flight Crew Instrument; Flight Crew Multiengine
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter CFTT / CFIT; Inflight Event / Encounter Object
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Became Reoriented
Contributing factors: Airport; Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: Well making an approach to Runway 02 at night impacted tops of tree branches on short final landed safely no injuries to pilot or passengers. I will be taking additional training with a CFI regarding approaches and landing at night.

Callback: The reporter stated that he had flown into this airport before and knew about the trees. He simply got too low on the approach. The only damage was dent in a wing.



Synopsis: A pilot reported impacting tree branches on short final during a night visual approach followed by a safe landing with no injuries.
Date: 201203
Local time of day: 0601-1200
Location: LAX.Airport, CA
Light: Daylight
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Taxi
ATC / advisory: Ground LAX
Aircraft component: Aero Charts
Component problem: Design
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Confusion; Situational Awareness
Anomaly: Deviation / Discrepancy - Procedural Clearance; Ground Incursion Taxiway
Detector: Person Air Traffic Control; Person Flight Crew
When detected: Taxi
Result: Air Traffic Control Issued Advisory / Alert; Air Traffic Control Provided Assistance
Contributing factors: Airport; Human Factors; Chart Or Publication
Primary problem: Airport

Narrative: During taxi; the clearance was E; R; D. Approaching the sign for R; the taxiway immediately to the right was the correct one. From our position it appeared that there was ground access (in green) only beyond that position. After turning onto that taxiway it was apparent that the turn should have occurred after the sign. The aircraft was stopped. Ground Control came on and said; 'That's not R.' We answered we realized that as the turn was completed. We were told to hold for a 'follow me' vehicle. We were guided back to E. Ground then cleared us via E; R; D to the gate. We apologized. He said that we were not the first to take that turn and probably won't be the last. The signage was misleading; the view indicated blockage beyond the point. Not stopping before the turn to verify with Ground Control. The problem remains that we were using the airport chart and still made the wrong decision.




Synopsis: LAX Taxiway R signage on Taxiway E misleads pilots to taxi into Taxiway E-13 because the sign is closer to E-13 than R.
Date: 201211
Local time of day: 0601-1200
Location: ZZZ.Airport, US
Flight conditions: VMC
Aircraft: A320
Operator: Air Carrier
Operating under: Part 121
Mission: Passenger
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Aircraft component: Landing Gear Indicating System
Component problem: Malfunctioning
Reporter organization: Air Carrier
Reporter function: First Officer; Pilot Flying
Second reporter function: Captain; Pilot Not Flying
Anomaly: Aircraft Equipment Problem Critical
Detector: Person Flight Crew
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; General Declared Emergency; General Maintenance Action
Contributing factors: Aircraft
Primary problem: Aircraft

Narrative: [We were] established on final [when] I called for the gear down; landing checklist. The Captain lowered the landing gear handle and we both noticed the left main landing gear light did not illuminate. After a very brief discussion we both decided not to attempt a landing. At approximately 1;000 feet we executed a normal go around and were cleared to 4;000 feet. At 4;000 feet we were vectored by ATC allowing time to declare an emergency; execute the Gear Disagree [checklist] and review the Partial Gear Landing checklist. After executing the appropriate checklists we were vectored to final; executed an uneventful landing and stopped straight ahead on runway.


Second narrative: [On final; after placing gear handle down] left main gear light did not illuminate. Pressed the light fixture and light did illuminate while being held in. Test switch on overhead panel would NOT illuminate the light. Between 1;000 feet and 500 feet we elected to go missed approach. Did a normal go around and accepted 4;000 feet and vectors. Advised flight attendants what was happening. Prior to downwind gear lever placed down with same results. Pressed light fixture numerous times with same results. Accomplished the Gear Disagree checklist including alternate gear extension with no improvement in the condition. Declared an emergency; asked company be notified and equipment standing by. Said we would stop straight ahead on the runway. Flight attendants told to prep for emergency landing with possible left gear collapse. Inside 500 feet I advised BRACE over the PA. Landed without incident. Advised [passengers] over PA to remain seated. Stopped on the runway. Met by crash equipment and awaited for Maintenance to arrive and pin all three gear. Taxied to gate without incident.


Synopsis: A320 flight crew reported left main gear light remained out after gear extension. They ran appropriate checklists; declared an emergency; and landed normally.