The Anatomy of Public Corruption

Target Careers: Sr Engineer - Oracle DBA job


Sr Engineer - Oracle DBA job

TARGETBROOKLYN PARK, MN
Target jobs
292
SR ENGINEER - ORACLE DBA
JOBS
119
JOBS IN
BROOKLYN PARK, MN
17
JOBS AT
TARGET

COMPANY DESCRIPTION

From our Minneapolis-based headquarters to over 1,800 stores and 38 distribution centers across the U.S., Target offers a world of possibilities in an environment that empowers its team members to innovate and contribute ideas. Join a company that’s focused on moving forward to what’s next while giving back to the communities they serve. Since 1946, Target has given five percent of its profit through community grants and programs; today, that giving equals millions of dollars a week.

JOB DESCRIPTION

Description: JOIN US AS A SENIOR ORACLE DBA Similar Industry Titles and Key Words: Oracle Database Administrator Use your skills, experience and talents to be a part of groundbreaking thinking and visionary goals. As a Senior Oracle DBA, you'll take the lead as you…
  • Design, plan, build and support an end to end technology stack supporting Target’s applications leveraging agile methodologies
  • Perform problem resolution for complex issues including root cause analysis, and outline resolution options
  • Use database expertise to identify and drive improvement efforts related to life cycle and patching of our database platform
  • Consult with development teams to advise on impacts of lifecycle and patching activities on the applications
  • Provide off-hours support, when required, for critical production issues.
  • Ensure process and technical documentation is complete per TTS (Target Technology Services) standards
  • Ensure high quality by participating in and following TTS processes
  • Provide application performance tuning activities, where needed
  • Participate in database strategic planning (business and technology trends)
  • Provide management and other team members clear and timely updates on status of assigned responsibilities
  • Stay current with technology and evaluate its impact on new and existing applications and platforms
  • Demonstrate growing application and technical knowledge
Requirements
  • BA/BS or equivalent experience
  • 8+ years total work experience
  • Has in-depth knowledge of state-of-the art engineering technical approaches in design, build, testing, debugging problems as required by domain
  • Maintains technical knowledge within areas of expertise
  • Stays current with new and evolving technologies via formal training and self-directed education
Preferred skills
  • 4-year college degree in computer science, engineering or math field
  • Master’s degree preferred
  • 5 years of Oracle DBA experience
  • Knowledge of PL/SQL language
  • Knowledge of DBMS query optimizer and query engine
  • Preferred background in development areas; some knowledge of Java and .NET
  • Experience in DBMS performance tuning
  • Ability to work with multiple development teams on multiple projects and manage priorities
  • Proven experience implementing and supporting the following Oracle features and functions: RAC, ASM, DataGuard, GoldenGate and Flash Recovery
  • Previous experience providing production database support in a 24x7 support organization
  • Experience working with Linux operating system
  • Experience providing database support in a large IT organization
  • Previous experience in infrastructure support
  • Previous experience working in agile environments
  • Understanding of infrastructure systems (e.g. server, storage, network, etc…)
  • Understanding of clustering and virtualization technologies
  • Understanding of retail business, technology, and the application of technology to our business
Share:

2003/10/30 - NIMDA / ANTHRAX / July 2003 the B of A Programmer Suicide

SECSYM: Security Symposium I



Most of the security vulnerabilities that have been found in Windows over the last
couple of years have not related to security features. For that reason, it's important
that every developer understands how to build secure code. Yet it's not something
that most people have had training on - it's not taught as part of most CS undergraduate
courses, for instance. At Microsoft, it's been a long road over the last couple of
years during which every developer has undertaken specific training on writing secure
code.
Security is becoming more challenging: the time-to-exploit has been decreasing (from
331 days for Nimda to 25 days to Blaster). There is no silver bullet to ensuring security
within a code base, it's something that takes a pervasive effort.
The Microsoft security framework comprises three key concepts: secure by design, secure
by default and secure in deployment - known as SD3. Secure by design means security-aware
features, and deliberate design to reduce vulnerabilities. Secure by default means
switching off unneeded features - unless 90% of users require a feature, the goal
in Windows is to switch that feature off on a clean installation. Finally, secure
by deployment means creating processes and guidance to deploy secure systems, along
with tools in the products to defend and update against vulnerabilities.
The SD3 approach includes a "Top 10" checklist:
  1. Build threat models: ensuring the design models potential attacks.
  2. Removing security flaws in source code: reviewing each line (against buffer overruns,
    for instance).
  3. Avoid new security flaws: for new code, being extra careful to prevent against flaws
    being introduced.
  4. Use managed code today: because it provides many intrinsic protections that can help
    reduce vulnerabilities.
  5. Use tools and checklists: books including Writing
    Secure Code
    , along with other patterns and practices (1 2).
  6. Turn features off: reducing attack surface by removing unneeded features that could
    be used in an exploit.
  7. Require minimum privilege: ensuring that even a successful exploit has limited value
    for compromising the machine.
  8. Add extra defensive layers: specific technologies to insulate an exploit from getting
    at the underlying system, as implemented in "Springboard" (see below).
  9. Be firewall and antivirus friendly: make sure that applications co-operate well with
    such environments.
  10. Create security guidance and documentation: giving the end-customer guidance on how
    to make their system more secure.
These approaches have been effective with recently released products. Subsequent to
the launch of the Trustworthy
Computing
 initiative, many products have completed full security reviews, checking
each line of code for potential vulnerabilities. For instance, Windows Server 2003
had 6 vulnerabilities in the first 180 days, compared to 21 vulnerabilities over the
first 180 days after the launch of Windows 2000 Server.
The aim too is to reduce the hassle of installing patches:
  • Reducing complexity: one patch experience
  • Reducing risk: better quality patches and a rollback capability for all patches
  • Reducing size: delta patching, enabling far smaller patches to download
  • Reducing downtime: doing everything possible to create patches that don't require
    reboots
  • Extending automation: making it easier to deploy patches using tools like Software
    Update Services
     and SMS
    2003
    .
Windows XP SP2 and Windows Server 2003 SP1 will include some new technologies (codenamed
"Springboard")
to add extra defensive mechanisms - inspecting packets, enabling the NX feature in
newer processors to create non-execute data pages, and to enable protection technologies
by default (such as ICF).
Windows XP SP2 will be in beta by the end of this year and released in the first half
of 2004; Windows Server 2003 SP1 will be in beta in the first half of 2004 and released
in the second half of 2004.
Share:

Case CIVMSC14-01974 - DODGE VS. RRS VENTURES and The Death Docket




BUCHANAN CONSTRUCTION & SONS, INC
Case CIVMSC14-01974 - DODGE VS. RRS VENTURES
Complaint Number: 1
Complaint Type: COMPLAINT
Filing Date: 10/28/2014
Complaint Status: DISMISS W/O PREJ. 10/31/2016
Party Number Party Type Party Name Attorney Party Status
1 PLAINTIFF MICHAEL DODGE BELOTE, JEFFREY H PARTY DISMISSED 10/31/2016
2 PLAINTIFF GWYNNETH DODGE BELOTE, JEFFREY H PARTY DISMISSED 10/31/2016
3 DEFENDANT RRS VENTURES, LLC ROSCHA, ESQ., NICHOLAS PARTY DISMISSED 10/31/2016
4 DEFENDANT BUCHANAN CONSTRUCTION & SONS, INC. SCHELEY, L THEODORE PARTY DISMISSED 10/31/2016
5 DEFENDANT S&J STADTLER INC. TAKANO, JESSICA M DISMISSED 08/19/2016
6 DEFENDANT RUSSELL K DARBY TAKANO, JESSICA M DISMISSED 08/19/2016
7 DEFENDANT J. ROCKCLIFF, INC. TAKANO, JESSICA M DISMISSED 08/19/2016
8 DEFENDANT ROBERT W GIBBS TAKANO, JESSICA M DISMISSED 08/19/2016
9 DEFENDANT DEBBIE M GIBBS TAKANO, JESSICA M DISMISSED 08/19/2016
Complaint Number: 2
Complaint Type: CROSS COMPLAINT
Filing Date: 02/17/2015
Complaint Status: DISMISS W/O PREJ. 11/29/2016
Party Number Party Type Party Name Attorney Party Status
3 CROSS COMPLAINANT RRS VENTURES, LLC ROSCHA, ESQ., NICHOLAS PARTY DISMISSED 11/29/2016
4 CROSS DEFENDANT BUCHANAN CONSTRUCTION & SONS, INC. SCHELEY, L THEODORE PARTY DISMISSED 11/29/2016
5 CROSS DEFENDANT S&J STADTLER INC. Unrepresented DISMISSED 08/19/2016
6 CROSS DEFENDANT RUSSELL K DARBY Unrepresented DISMISSED 08/19/2016
7 CROSS DEFENDANT J. ROCKCLIFF, INC. Unrepresented DISMISSED 08/19/2016
10 CROSS DEFENDANT ROCKCLIFF REALTORS Unrepresented PARTY DISMISSED 11/29/2016
11 CROSS DEFENDANT ROBERT W GIBBS Unrepresented DISMISSED 08/19/2016
12 CROSS DEFENDANT DEBBIE M GIBBS Unrepresented DISMISSED 08/19/2016
Complaint Number: 3
Complaint Type: CROSS COMPLAINT
Filing Date: 03/19/2015
Complaint Status: DISMISS W/O PREJ. 12/16/2016
Party Number Party Type Party Name Attorney Party Status
4 CROSS COMPLAINANT BUCHANAN CONSTRUCTION & SONS, INC. SCHELEY, L THEODORE PARTY DISMISSED 12/16/2016
3 CROSS DEFENDANT RRS VENTURES, LLC ROSCHA, ESQ., NICHOLAS DISMISSED 09/07/2016
5 CROSS DEFENDANT S&J STADTLER INC. Unrepresented DISMISSED 08/19/2016
6 CROSS DEFENDANT RUSSELL K DARBY Unrepresented DISMISSED 08/19/2016
7 CROSS DEFENDANT J. ROCKCLIFF, INC. Unrepresented DISMISSED 08/19/2016
11 CROSS DEFENDANT ROBERT W GIBBS Unrepresented DISMISSED 08/19/2016
12 CROSS DEFENDANT DEBBIE M GIBBS Unrepresented DISMISSED 08/19/2016

Share:

NTSB: Peter and Mona Branagh Cirrus SR22, Springhill Aviation LLC, N86AA: Fatal accident occurred July 14, 2012 in Salina, Utah

.kathryn sreport.com - Peter Branagh

Cirrus SR22, Springhill Aviation LLC, N86AA: Fatal accident occurred July 14, 2012 in Salina, Utah

Aviation Accident Final Report - National Transportation Safety Board:https://app.ntsb.gov/pdf 

Docket And Docket Items -   National Transportation Safety Board:https://dms.ntsb.gov/pubdms

NTSB Identification: WPR12FA305
14 CFR Part 91: General Aviation
Accident occurred Saturday, July 14, 2012 in Salina, UT
Probable Cause Approval Date: 10/30/2014
Aircraft: CIRRUS DESIGN CORP SR22, registration: N86AA
Injuries: 2 Fatal.

NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

The noninstrument-rated pilot departed on a visual flight rules (VFR) cross-county flight. Recorded radar data indicated that the airplane was in level flight at 13,300 feet mean sea level (msl) during about the last 30 minutes of the flight. The last 2 minutes of the radar data showed the airplane making a slow climbing turn to an altitude of 14,200 feet msl. The last radar returns showed the airplane making a sharper left turn at 13,500 feet msl before radar contact was lost. The accident site was located 1.5 nautical miles southeast of the last radar return at an elevation of 7,928 feet msl. Examination of the accident site revealed that the airplane collided with trees and mountainous terrain in a steep nose-down attitude. A postaccident examination of the airframe and engine revealed no evidence of preimpact mechanical malfunctions or failures that would have precluded normal operation. It could not be determined if the pilot obtained a weather briefing for the flight. The most recent pilot report before the accident indicated cloud bases at 9,000 feet in the accident area. Weather returns depicted light-intensity echoes over the route of flight consistent with reduced visibility in light rain and extensive vertically developed clouds. Therefore, although weather conditions at the departure and destination airports were VFR, available weather information indicates that the accident airplane likely encountered instrument meteorological and mountain obscuration conditions en route. Given the weather conditions in the area and the altitude and course changes made in the few minutes before the accident, it is likely that the pilot became spatially disorientated and subsequently lost airplane control. 

The National Transportation Safety Board determines the probable cause(s) of this accident as follows:
The noninstrument-rated pilot’s continued visual flight into instrument meteorological conditions, which resulted in spatial disorientation and a subsequent loss of airplane control.

HISTORY OF FLIGHT

On July 14, 2012, about 1130 mountain daylight time (MDT), a Cirrus SR22, N86AA, impacted terrain near Salina, Utah. Springhill Aviation LLC., was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot and one passenger were fatally injured; the airplane was substantially damaged by impact forces. The local cross-country personal flight departed Concord, California, with a planned destination of Aspen, Colorado. Visual and instrument meteorological conditions prevailed along the route of flight, and a visual flight rules (VFR) flight plan had been filed.

The airplane was the subject of an alert notice (ALNOT) following the loss of radar contact. Local law enforcement and the Civil Air Patrol initiated a search for the airplane. The wreckage was located by personnel from the Sevier County Sheriff's department flying in a civilian provided helicopter at about 1800 MDT, on July 15, 2012.

Radar data obtained for the flight from the Federal Aviation Administration (FAA) was reviewed by the National Transportation Safety Board (NTSB) investigator-in-charge (IIC). The radar track identified the airplane traversing from west to east at a Mode C altitude of 13,700 feet mean sea level (msl). During the last 2 minutes of radar data, the radar target indicated a slow climbing turn to an altitude of 14,200 feet msl. The last radar return was at 11:28:54 MDT, that indicated a sharper left turn at a reported altitude of 13,500 feet msl before radar contact was lost. The accident site was located 1.5 nautical miles (nm) southeast of the last radar return. The field elevation at the accident site was 7,928 feet msl. An Air Traffic Control Study was completed by an air traffic investigator and is attached to the public docket.

PERSONNEL INFORMATION

The 59-year-old pilot held a private pilot certificate with a single engine land rating. He held a third-class medical certificate dated April 25, 2012, with the limitation: must have available glasses for near vision. The medical certificate stated the pilot was 73 inches tall and weighed 245 pounds.

According to the Cirrus corporate flight operations department, the pilot had not received any transition training from Cirrus.

The pilot's logbook was recovered from the accident site. The logbook covered entries from December 28, 2003, through June 26, 2012.

According to the logbook entries, the pilot began his initial flight training in the end of December 2003. The bulk of his private pilot training was conducted in a Cessna 172 with a few lessons in a Cirrus model SR20.

A February 14, 2005, logbook entry showed an instructional flight from Klamath Falls, Oregon, to Redding, California, and the remarks block states "picked up SR22." The registration annotated was for N86AA, the accident airplane. No further flights were listed for N86AA until July 2005, which was after the pilot took his private pilot practical written test.

On June 20, 2005, the pilot took and passed his private pilot practical flight exam in a Cessna 172 with about 211 flight hours logged. After the private pilot's test, two flights are logged in a Cessna 172. Mid July 2005, the pilot started to receive instruction in the accident airplane.

The logbook indicates the pilot had biennial flight reviews in 2007, 2009, 2010, and 2011.

Cirrus Owners Pilot Association (COPA) records show that the pilot attended a COPA Cirrus Pilot Proficiency Program (CPPP) event in Concord, California, in October 2008, as a "ground participant." The pilot's logbook indicates he also attended a COPA CPPP in October 2012, where he did log flight time.

According to the pilot's logbook entries he had accumulated a total flight time of 600 hours, with 484 hours in the accident make and model. The pilot had flown 7.5 hours in the last 90 days, 1.3 in the last 30 days, and zero hours in the last 24 hours.

AIRCRAFT INFORMATION

Cirrus SR22 serial number 1131, registration number, N86AA, received its standard airworthiness certificate on October 19, 2004. The airplane was equipped with: an S-TEC 55X autopilot, TKS anti-icing system, Avidyne Primary Flight Display (PFD) & Multi-Function Display (MFD), dual Garmin GNS430s, engine monitoring, Sky Watch, and XM weather.

According to documents on file, the airplane was purchased new in October 2004, by the pilot directly from Cirrus.

Airframe total time was undetermined.

No airplane records were located at the accident site, and the pilot's family was unable to locate any maintenance records for the airplane.

According to records obtained from Sterling Aviation in Concord, a 100-hr/annual inspection had been completed, and the airplane returned to service on October 27, 2011, with an airframe total time of 588.7 hours.

METEOROLOGICAL CONDITIONS

A staff meteorologist for the NTSB prepared a weather study, which included the following weather for the departure area, route of flight, and destination.

A review of the Mesowest data for remote weather observation equipment indicated several sites within 30 miles of the accident site. Joe's Valley situated at 8,700 feet was the closest weather reporting station. It was located 28 miles north of the accident site, and under similar conditions based on the satellite image reported a temperature of 53 degrees Fahrenheit, dew point of 51 degrees Fahrenheit, a relative humidity of 94%, and indicated reduced visibility and/or a ceiling less than 1,000 feet supporting mountain obscuration conditions. The wind was from the south-southwest at 5 knots.

In-Flight Weather Advisories – The national Weather Service (NWS) had the following advisories current over the region: A Convective Significant Meteorological Information (SIGMET) 54W for an area of embedded thunderstorms in the area immediately south of the accident site moving north at 20 knots with tops to 43,000 feet, and an Airmen's Meteorological Information (AIRMET) for mountain obscuration.

Summary - The observations from Price, Utah (KPUC), indicated multiple layers of clouds and rain showers with VFR conditions, while conditions at Bryce Canyon (KBCE) south of the accident site and at almost the same elevation of Price, reported LIFR conditions due to rain, fog/mist, with ceilings broken to overcast between 200 and 400 feet agl at the time of the accident. Based on conditions at Bryce Canyon ceilings over the accident site may have been at 8,000 feet msl with visibility restricted in rain.

The RAWS site at Joes Valley at 8,700 feet msl did not have a visibility or ceilometer; however, the station reported a 94% relative humidity with a 1-degree temperature-dew point spread, which supported low ceilings and/or visibility in rain/mist. Other RAWS sites in the higher elevation reported similar conditions.

A pilot report at 1138 MDT (1738Z) from a Beechcraft BE35 at 7,500 feet reported 20 miles north of Cedar City, Utah, immediately west of the accident site that the mountains were obscured. Conditions at Bryce Canyon also reported similar conditions with the 200 to 400 feet ceilings. Another report from a Cessna CRJ flying over the Cedar City area reported cloud bases at 9,000 feet with icing conditions between 12,000 and 13,000 feet. Other aircraft reported isolated rain showers in all quadrants, with some producing moderate to heavy precipitation.

The radar and satellite imagery depicted convective clouds over the route and the accident site with tops to 27,500 feet, with conditions very similar to what was observed over Bryce Canyon. The radar imagery from Cedar City (KICX), 0.5-degree base reflectivity image was centered at 22,600 feet and depicted very light intensity echoes over the accident site and implied cumulus congestus clouds capable of producing rain showers and reduced visibility.

The NWS Aviation Weather Center's (AWC) Area Forecast expected scattered clouds at 12,000 feet msl and broken at 15,000 feet with tops to 28,000 feet. The forecast was amended by an AIRMET for mountain obscuration that extended over the route and the accident site.

The Terminal Area Forecast (TAF) for Bryce Canyon available to the pilot at the time of departure indicated a temporary period of Instrument Flight Rules (IFR) conditions in rain showers near the time of the accident. The TAF was amended at 1012 MDT (1612Z) to reflect actual conditions, which was IFR with ceilings broken at 200 feet until 1100 MDT with thunderstorms in the vicinity afterwards. The TAF did not verify actual conditions during the period as IFR conditions prevailed during the entire period. The original forecasts implied VFR conditions would prevail, which did not verify based on observations.

COMMUNICATIONS

The airplane had been in contact with Salt Lake City, Air Route Traffic Control Center (ARTCC) Center on frequency 125.57.

The following transcript was from recorded communications between ATC (ZLC44) and N86AA.

1710:48-ZLC44

NOVEMBER EIGHT SIX ALPHA ALPHA, RADAR CONTACT LOST, SAY ALTITUDE

1710:52-N86AA 

UH, THIRTEEN THOUSAND FIVE HUNDRED

1710:56-ZLC44

NOVEMBER SIX ALPHA ALPHA ROGER UHM, WE WON'T PICK YOU UP FOR A WHILE, RADAR SERVICE IS TERMINATED, SQUAWK V F R, FOR FURTHER FLIGHT FOLLOWING, AS YOU'RE APPROACHING THE UH, CANYON LANDS AREA, YOU CAN TRY DENVER CENTER ON UH, LET'S SEE, IT'LL BE UH, ONE THREE FOUR POINT FIVE AS YOU UH, GET CLOSE TO THE MOAB AREA

1711:19-N86AA

OKAY, ONE THREE, ONE THREE POINT FIVE, RIGHT NOW I'M OVER RICHFIELD, THANK YOU

1711:24-ZLC44

NOVEMBER SIX ALPHA ALPHA ROGER, SQUAWK V F R, RADAR SERVICES TERMINATED, THIRTY-FOUR POINT FIVE AROUND CANYON LAND

1711:29-N86AA

THIRTY-FOUR POINT FIVE, THANK YOU

No further communications with the accident airplane were obtained.

WRECKAGE AND IMPACT INFORMATION

The accident site was located on the northern slope of a ridgeline in the Fishlake National Forest. The debris field was roughly 100 feet wide by 425 feet long running parallel to the crest of the ridge from east to west. The energy path was 263 degrees magnetic.

The first point of impact was a pine tree, which had its trunk broken at approximately 17 feet up. A ground scar was noted 30 feet beyond the broken pine tree, and was approximately 3-to-4 feet wide and 15 feet in length, ending at the crater that contained the engine firewall, and portions of the center console structure; the crater was about 3 feet deep. For the purposes of this report, the crater location was referred to as the "main wreckage, and was located at north 38 degrees, 49.181 minutes latitude and west 111 degrees, 25.948 minutes longitude, at an elevation of 7,928 feet msl.

In the immediate vicinity of the crater were several trees, whose mud spattered trunks faced opposite of the energy path of the accident airplane.

The engine came to rest oriented along a 200-degree magnetic heading. A propeller blade that had separated from the propeller hub, protruded from the crater just prior to the engine. Another propeller blade protruded from the dirt just forward of the engine oriented in the direction of the energy path. When moved by hand the blade felt as though it were still anchored to the propeller hub under the surface of the dirt. Recovery personnel later confirmed the propeller blade remained connected to the propeller hub assembly.

The airplane had fragmented during the accident sequence, with wing skin fragments located 70 feet away from the main wreckage nestled in the trees' limbs. The entire airplane was accounted for, and all damage was attributed to accident forces. The accident field report for this accident is attached to the public docket.

The PFD was present in the debris field. The screen was missing and the case was deformed with portions of the case missing. The internal circuit boards for the PFD were fragmented and separated from the PFD case. The PFD circuit cards were recovered for further examination.

The MFD memory module (compact flash card) was co-located in the debris field with the PFD.

MEDICAL AND PATHOLOGICAL INFORMATION

The Sevier County Coroner completed an autopsy on July 18, 2012. The FAA Civil Aerospace Medical Institute (CAMI), Oklahoma City, Oklahoma, performed toxicological testing of specimens of the pilot.

The cause of death was blunt force injuries as a result of an airplane accident.

Review of all FAA medical certificates and supporting documentation indicated that the pilot reported no significant past medical history and the Airman Medical Examiner (AME) identified no significant issues on physical examination.

Toxicological analysis could not be conducted due to tissue putrefaction. As a result, no determination could be made as to whether tested-for-drugs or ethanol had posed a hazard to flight safety.

Based on available history and physical examinations; the pilot has no known medical issues that would pose a hazard to flight safety.

TESTS AND RESEARCH

On August 14, 2012, the recovered airplane and engine were examined at Air Transport Inc., Phoenix, Arizona, by the investigation team and the reports are included in the accident docket.

The airframe and engine were examined with no mechanical anomalies identified that would have precluded normal operations.

The PFD and MFD were shipped to the NTSB Vehicle Recorders Laboratory for further examination. The Vehicle Recorders specialists reported that circuit cards were the correct cards but the chips containing data were not present on the boards. No data was recovered from any of the recovered components.

 http://registry.faa.gov/N86AA
  
 NTSB Identification: WPR12FA305 
14 CFR Part 91: General Aviation
Accident occurred Saturday, July 14, 2012 in Salina, UT
Aircraft: CIRRUS DESIGN CORP SR22, registration: N86AA
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. NTSB investigators either traveled in support of this investigation or conducted a significant amount of investigative work without any travel, and used data obtained from various sources to prepare this aircraft accident report.

On July 14, 2012, about 1130 mountain daylight time (MDT), a Cirrus Design Corp SR22, N86AA, impacted terrain near Salina, Utah. Springhill Aviation LLC, was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot and one passenger were fatally injured; the airplane sustained substantial damage from impact forces. The local cross-country personal flight departed Concord, California, with a planned destination of Aspen, Colorado. Visual and instrument meteorological conditions prevailed along the route of flight, and no flight plan had been filed.

The airplane was a subject of an ALNOT following the loss of radar contact. Local law enforcement and the Civil Air Patrol initiated a search for the airplane. The airplane was located by personnel from the Sevier County Sheriff’s department flying in a civilian provided helicopter about 1800, on July 15, 2012.

The radar track for the flight was reviewed by the National Transportation Safety Board investigator-in-charge (IIC). It indicated that while traversing from west to east at a Mode C reported altitude of 13,700 feet mean sea level (msl), and during the last 2 minutes of recoded radar data, the target climbed to an altitude of 14,200 feet msl. The last radar return was at 11:28:54, at 13,500 feet msl. The accident site was located 1.5 nautical miles (nm) southeast of the last radar return.

The preliminary review of weather in the area of the accident indicated that the cloud base was at 9,000 feet msl, and the cloud top was at 27,000 feet msl with light rain.

Investigators examined the wreckage at the accident scene. The accident site was located on the northern slope of a ridgeline in the Fish Lake National Forest. The debris field was roughly 100 feet wide by 425 feet long running parallel to the crest of the ridge from east to west, with a debris path along a 263-degree magnetic heading. The first point of impact was a pine tree; the trunk was broken approximately 17 feet from the base of the tree. A ground scar was noted 30 feet beyond the broken pine tree. The ground scar was roughly 3-4 feet wide and continued for 15 feet ending in a crater that was approximately 2 to 3 feet deep with the engine, firewall, and some of the center console structure buried at the end of the crater.

The accident site was documented and the airplane and engine were recovered for further examination.
 

  
Peter and Mona Branagh were flying their single engine craft to Aspen when it struck mountainside 

Memorial services will be held in Danville Saturday for East Bay developer Peter Branagh and his wife Mona who were killed when the small plane they were flying crashed into a mountainside in southern Utah.

Nr. Branagh was president of Branagh Development, a well-known development firm with with extensive interests in Pleasanton's downtown and residential communities. Mrs. Branagh owned and operated Pacific Bay Interior in Danville.

Both were members of the California Bank of Commerce's founding group where Mr . Branagh was also a director.

The couple, who lived Lafayette, was traveling in a single engine Cirrus SR22 from a stop in Utah to Aspen, Colo. when the plane crashed into a mountainside north of I-70 about 27 miles southeast of Salina, Utah. Sevier County (Utah) Sheriff Nathan Curtis, who went to the site Tuesday, told the Salt Lake Tribune that based on some of the electronic devices that he found, the couple was flying at 14,000 feet before the plane plummeted down into the mountain.

Partnering with Craig Semmelmeyer, president of Main Street Property Services, Inc. in Lafayette, Peter Branagh was involved in the development of the building at Angela and Main Street in Pleasanton that is home to Tully's Coffee Shop and the more recent renovation of the 234 Main Street building, where Fleet Feet sports specialty store is located and eventually a restaurant will be added. Branagh's company also built homes in Ruby Hill.

Saturday's memorial service wil be held starting at 1 p.m. Saturday at the Community Presbyterian Church, 222 W. El Pintado Road in Danville.

LAFAYETTE -- A well-known local developer and his wife died in a private plane crash over the weekend in the mountains of central Utah, officials said. 

 California Bank of Commerce Director Peter Branagh and his wife Mona were flying in a small plane from Danville to Aspen, Colo., on Saturday, but never arrived, prompting family members to call authorities.

A private helicopter crew hired by the family finally found wreckage believed to be from the plane Sunday in a remote canyon of Sevier County, Utah, according to Sheriff Nathan Curtis.

The area is an isolated patch of mountain desert, more than 20 miles from the nearest town. Investigators were still looking into the details of the crash Monday.

An e-mail from Peter Branagh's firm, Branagh Development, confirmed Monday the couple had died.

The company will close its doors until Thursday, the e-mail said, adding, "Please bear with us as we mourn the tragic loss of Peter and Mona Branagh, who passed away this weekend in an airplane crash."

The couple were Lafayette residents for many years and Peter Branagh helped beautify and improve the community through developments, Lafayette City Manager Steven Falk said Monday.

Branagh and his firm were responsible for numerous projects throughout the city, perhaps most notably the Hidden Oaks housing development near Condit Road, Falk said. Completed about five years ago, it includes more than 20 new high-end homes, he said.

"It  is just an absolutely gorgeous project," Falk said. "When we started, this was a piece of raw land, and rather than cut all the trees down and build as many houses as possible, Peter insisted on preserving all the mature oaks around the houses. That attention to detail and sensitivity for the environment distinguished Peter as a developer."

Falk said he'd worked with Branagh for about a decade on numerous projects.

"I think it's just a giant loss for our community," he said.

Members of the Branagh family could not immediately be reached, and California Bank of Commerce officials declined to comment. 

RICHFIELD — The wreckage of a plane believed to have been carrying a couple from Northern California to Aspen, Colo., is being recovered in Sevier County. 

Family members started calling authorities for signs of the overdue plane on Saturday night, hoping the couple had made an emergency landing somewhere, according to the Sevier County Sheriff's Office.

Radar indicated the last place the aircraft was tracked was near the borders of Sevier, Emery and Sanpete counties. In addition to a search from the Civil Air Patrol, family members got a private helicopter and assisted in the search themselves.

The helicopter located a "debris field" Monday in a rugged area in Saleretus Canyon, sheriff's deputies said. The National Transportation Safety Board and the Federal Aviation Administration were assisting in the recovery and investigative effort.

There were no reports of survivors. The names of the people traveling were not immediately released.

If the pilot and passenger are confirmed as being killed in the crash, it would mark the 14th and 15th people killed in plane crashes in Utah this year. Eleven people were killed in plane crashes in Utah in all of 2011, according to the NTSB.

A Lafayette couple died when their small plane crashed in Utah over the weekend, friends and authorities said Monday.

Local home developer Peter Branagh, 59, and his wife, interior designer Ramona Branagh, 57, died when their Cirrus SR22 crashed in a remote canyon near Richfield, Utah, on Saturday. The couple had been heading for Aspen, Colo.

Family members became worried after the couple failed to arrive in Aspen, said Sheriff Nathan Curtis of Sevier County, Utah.

"Family started calling for assistance on Saturday evening to help see if the plane had landed at unmanned airports in the area," Curtis said. "It was hoped they had some mechanical problems and landed somewhere off radar."

Private helicopters hired by the family found the crashed plane.

The couple's plane, built in 2004, had no record of problems, according to federal aviation databases. The cause of the crash is under investigation by the National Transportation Safety Board.

"This is a gigantic loss for the Lafayette community," City Manager Steve Falk said Monday. "The thing that distinguished the many conversations I had with Peter over the years was that we would talk almost constantly about quality. That was always his first concern, and that made him different than many, if not most, developers."

Peter Branagh was a director of the California Bank of Commerce in Lafayette and was president of Branagh Development in Danville.

He and his wife, known as Mona, owned Pacific Bay Interiors at the White House, a design business in Danville.

The design store's website said the couple "fell in love with the architecture and style of colonial Williamsburg" while visiting the East Coast. "Their vision was to bring the classic East Coast style to the West."
RICHFIELD, Utah – A single-engine plane crashed in Sevier County killing two people. 

A Cirrus SR22 single-engine plane crashed in mountainous terrain under unknown circumstances, Allen Kenitzer with the FAA said.

On Saturday, the Sevier County Sheriff’s Office received a call when a party traveling from California to Aspen, Colo. failed to arrive.

Sheriff Nathan Curtis said they believe the missing party was on the crashed plane. The identities of the victims are not being released at this time.

The NTSB and FAA are investigating the accident to determine a cause of the crash.
Share:

The Mel Carnahan Plane Crash


Share:

Special Counsel Mueller on PanAm -


Share:

Anchor links for post titles

Popular Posts

Blog Archive

Labels

Recent Posts

Popular Posts

Labels

Recent Posts

Pages

Labels

Blog Archive

Recent Posts