Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Things that make you go HMMM.....

  • Thread starter Thread starter 350DRIVER
  • Start date Start date
  • Watchers Watchers 3

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
3

350DRIVER

>Its sad two people died but what were they thinking:check out this accident

in HRO
>Well Jim L has gone goofy on flying -- I actually thought I was going to
>have a Sunday off and then he starts freakin out this weekend now I'm
>getting calls at the last hour to fly ...I swear this guy either does not
>know were he wants to go minute to minute or he just doesnt give a **CENSORED****CENSORED****CENSORED****CENSORED**
>and expects us to be there at a whim with no notice ...unfortunately I know
>that there have been times when he knew well in advance ....I just don't
>think he gives a **CENSORED****CENSORED****CENSORED****CENSORED**...oh well If he keeps it up it will just push me out
>of the comfort zone and I'll have to look elsewhere down the road. Anyway
>this last three days has been a little frustrating.-- Ok we are absolutely
>not flying on Sunday no way we are flying ...go ahead and plan a day with
>the family (first time since I have worked there) then the phone rings at
>8am hey we got to fly this afternoon so screw your day....I don't want to
>drive home from west memphis were I have been duck hunting and Gary George
>was hunting with me and left early today....I could have hitched a ride
>with him...but no screw it I want to stay down here a few more hours so you
>guys eat **CENSORED****CENSORED****CENSORED****CENSORED** and come pick me up ... ugh....
>
>NTSB Identification: FTW04FA036
>14 CFR Part 91: General Aviation
>Accident occurred Thursday, December 04, 2003 in Harrison, AR
>Aircraft: Beech S35, registration: N350JL
>Injuries: 2 Fatal.
>
>This is preliminary information, subject to change, and may contain errors.
>Any errors in this report will be corrected when the final report has been
>completed.
>
>On December 4, 2003, approximately 1006 central standard time, a Beech S35
>single-engine airplane, N350JL, registered to and operated by a private
>individual, was destroyed when it impacted the ground while on final
>approach to runway 36 at Boone County Airport (HRO), Harrison, Arkansas.
>The instrument rated private pilot and passenger were fatally injured.
>Instrument meteorological conditions (IMC) prevailed, and an instrument
>flight rules (IFR) flight plan was filed for the 14 Code of Federal
>Regulations Part 91 cross-country flight. The personal flight departed
>Adams Field Airport (LIT), Little Rock, Arkansas approximately, 0912, with
>a planned destination of Boone County Airport (HRO), Harrison, Arkansas.
>
>According to air traffic control, the airplane was cleared for an ILS
>approach to runway 36. Air traffic control data was reviewed by the NTSB
>investigator-in-charge (IIC), and all times converted to central standard
>time unless otherwise noted. At 0019, the pilot contacted Jonesboro Flight
>Service Station (JBR FSS) via telephone, requested and received an outlook
>briefing for the planned route of flight. At 0706, the pilot contacted JBR
>FSS, requested and received a standard weather briefing. At 0826, the pilot
>filed an IFR flight plan (in part: N350JL, true airspeed 170 knots,
>altitude 6,000 feet msl, time en route 45 minutes, fuel on board 5 hours)
>from LIT to HRO.
>
>At 0910, the airplane was cleared for takeoff by the controller at the
>Little Rock Air Traffic Control facility, and was instructed to climb to
>6,000 feet msl.
>
>At 0925, the pilot was cleared to contact Memphis Air Route Traffic Center
>(MEM ARTCC).
>
>At 0956, the flight was cleared for the ILS 36 approach at HRO.
>
>At 1006, the pilot reported to the controller (MEM ARTCC) that he was on a
>1/4 mile final for runway 36. There were no additional ATC communications
>with the pilot.
>
>Numerous witnesses observed and heard the airplane. One witness, a Fixed
>Base Operator (FBO) employee, manning the Unicom frequency, stated that
>approximately 1000, the pilot transmitted that the airplane was over Bakky
>(initial approach fix for ILS 36) and wanted to know if there was other
>aircraft in the area. A few moments later, the pilot radioed that he
>[airplane] was coming in a "little" high on the approach and was going to
>do a downwind for runway 36.
>
>This Unicom operator observed the airplane at an estimated altitude of 300
>to 400 feet agl, approximately midfield, turn crosswind for runway 36. This
>witness stated that the airplane "overshot" the runway on the base to final
>turn, and enter a steep turn from base to final.
>
>A second witness, who saw the airplane flying "real low" reported the
>airplane was flying south, then banked "real sharp" toward the east. Then
>the airplane banked "hard" towards the north, the nose "shot" up in the
>air, the airplane pivoted, and headed straight down.
>
>A third witness, who was outside the commercial building on the west side
>of the airport, said she heard an airplane coming from the north. The
>airplane continued to get louder so she knew it was low, and looked up to
>see the airplane flying over. The airplane came over the building at about
>40 to 50 feet, and just missed the roof. The wheels cleared the trees
>(approximately 50 feet tall) about 15 yards south of the building. After
>clearing the trees, the airplane started a left turn toward the runway.
>
>A fourth witness, who was west bound in his truck, saw the airplane flying
>"very low" approximately 50 to 60 feet above the runway lights. The
>airplane, flying from north to south, made a "hard" left turn to the east.
>
>A fifth witness, who was sitting in his vehicle, observed the airplane
>flying east, make a left bank where the bottom of the airplane was toward
>the witness. During the left bank the nose went up, the airplane twisted,
>and nosed straight down toward the ground.
>
>Witnesses called 911, and the local authorities responded to the accident
>site. The local authorities reported that the impact was non survivable.
>
>The Global Positioning System (GPS) location of the accident site was
>latitude 36 degrees 14.95 minutes North; longitude 093 degrees 09.29
>minutes West in approximately a 15-foot drainage area located at the
>southeast portion of the airport. The main wreckage came to rest upright on
>a measured magnetic heading of 100 degrees.
>
>Initial examination of the airplane, engine, and propeller was conducted at
>the accident site on December 5 and 6, 2003, under the supervision of the
>NTSB IIC. The airplane was recovered by Dawson Aircraft, Inc., Clinton,
>Arkansas, for further examination under the supervision of the NTSB IIC.
>
>Index for Dec2003 | Index of months
 
Gee whiz. Fix that formatting before you post. It might have made me go hmmm if I could read it.
 
hmmm....SNAFU!
 
Sad. Going missed and making a second approach might have done the trick. Trying to maneuver below the cloud deck is foolish.

Too much airplane, not enough skill.

Hmmm.
 
Gee whiz. Fix that formatting before you post. It might have made me go hmmm if I could read it.

av- was actually sent to me via an email so I just copied and pasted it without knowing how the text would appear in this post. They do say the much older one gets the much harder it is to read text in that form.:D J/K! !

c h e e r s

3 5 0
 
350, That would explain a lot. A lot of things get harder the older you get...and for the ones that don't, there's always help ;) .


You can always use the edit feature to go back and fix something like that. The question is, is it really worth the time to do so?
 
You can always use the edit feature to go back and fix something like that. The question is, is it really worth the time to do so?


I agree and the point is taken to heart for future posts from forwards that I post. It does look a little off in "right field" after looking at it again.


c h e e r s

3 5 0
 

Latest resources

Back
Top