<?xml version="1.0"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

<channel>
<title>U.S. DoT OIG MARAD RSS Feed</title>
<link>http://www.oig.dot.gov/rss.jsp?agency=8</link>
<description>The 10 most recent releases on the U.S. DoT OIG web site ... MARAD</description>
<language>en-US</language>
<webMaster>webmaster@oig.dot.gov (OIG Webmaster)</webMaster>
<image>
<url>http://www.oig.dot.gov/images/dot.gif</url>
<title>U.S. DoT OIG MARAD RSS Feed</title>
<link>http://www.oig.dot.gov/rss.jsp?agency=8</link>
</image>
<atom:link href="http://www.oig.dot.gov/rss.jsp?agency=8" rel="self" type="application/rss+xml" />
<item>
<title>Status of Operating Administrations Processes to Conduct Limited Quality Reviews of Recovery Act Recipient Data</title>
<link>http://www.oig.dot.gov/item.jsp?id=2547</link>
<description>On October 6, 2009, we issued our report on the Department of Transportation Operating Administrations plans for ensuring Recovery Act fund recipients submit accurate, complete, and timely data on the use of these funds, as required by Section 1512 of the Recovery Act.  Office of Management and Budget (OMB) guidance states that starting October 22, 2009, Federal agencies are to perform a limited data quality review of recipient information and notify the recipients of two key data problemsmaterial omissions and significant reporting errors.  Our audit objective was to determine whether the Departments Operating Administrations have established processes to perform such reviews and notify recipients of the need to make appropriate and timely changes.  We found that the Departments Operating Administrations overseeing the implementation of the Recovery ActFederal Aviation Administration (FAA), Federal Highway Administration (FHWA), Federal Railroad Administration (FRA), Federal Transit Administration (FTA), and Maritime Administration (MARAD)have taken steps to ensure that Recovery Act recipients comply with Section 1512 reporting requirements.  These steps range from conducting outreach to recipients regarding the specific reporting requirements to drafting processes for performing limited data quality reviews.  Each Operating Administration aims to have a process in place before conducting the reviews, and as of September 25, 2009, two of five Operating AdministrationsFAA and FTAhave drafted processes.  However, it is too early to determine whether these processes will adequately identify omissions and significant reporting errors.  As we continue to conduct our Recovery Act work, we will monitor the Operating Administrations progress, and may conduct additional work of the adequacy of Operating Administrations and recipients internal control procedures for ensuring data quality.</description>
<pubDate>Tue, 06 Oct 2009 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2547</guid>
</item>
<item>
<title>American Recovery and Reinvestment Act: DOTs Implementation Challenges and the OIGs Strategy for Continued Oversight of Funds and Programs</title>
<link>http://www.oig.dot.gov/item.jsp?id=2456</link>
<description>On April 30 the Inspector General testified before the Senate Committee on Appropriations, Subcommittee on Transportation, Housing and Urban Development, and Related Agencies, regarding the Department of Transportations (DOT) oversight of the American Recovery and Reinvestment Act (ARRA) and OIGs related audit and investigative strategy.  In anticipation of ARRAs passage, we initiated a threephase approach to conducting related work.  We completed Phase 1 with the issuance of our March 31, 2009 report on key oversight challenges facing DOT.  We also identified several ongoing audits that have a direct connection to the programs funded under ARRA and related requirements.  We plan to fasttrack the most timesensitive results of our work on these audits to ensure we provide DOT, Congress, and taxpayers with timely and relevant information.   We have started Phase 2 of our strategy, which involves systematic reviews of the DOT agencies that received funding in ARRA.  These scans will examine vulnerabilities in program management and planning that could impede DOTs ability to provide effective oversight of ARRAfunded projects and meet new statutory and Office of Management and Budget requirements.  We plan to begin reporting the results of Phase 2 this summer.  Phase 3 is a longterm initiative in which we will drill down on highrisk areas that emerge as a result of our agency scans.</description>
<pubDate>Thu, 30 Apr 2009 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2456</guid>
</item>
<item>
<title>DOT OIG Economic Recovery Oversight Plan</title>
<link>http://www.oig.dot.gov/item.jsp?id=2457</link>
<description>The American Recovery and Reinvestment Act (ARRA) of 2009 designated $20 million to DOT OIG through Fiscal Year 2013 to conduct audits and investigations of DOT projects and activities funded by ARRA.  In anticipation of ARRAs passage, we initiated a threephase approach to conducting related audit and investigative work, expanded our investigative outreach efforts, and maximized new funding and program flexibilities.  The actions we have taken and plan to take will help position our Office to meet the increased workload under ARRA and protect the Federal investment over the long term.</description>
<pubDate>Wed, 29 Apr 2009 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2457</guid>
</item>
<item>
<title>American Recovery and Reinvestment Act: DOTs Implementation Challenges and the OIGs Strategy for Continued Oversight of Funds and Programs</title>
<link>http://www.oig.dot.gov/item.jsp?id=2455</link>
<description>On April 29 the Inspector General testified before the House Committee on Transportation and Infrastructure regarding the Department of Transportations (DOT) oversight of the American Recovery and Reinvestment Act (ARRA) and OIGs related audit and investigative strategy.  In anticipation of ARRAs passage, we initiated a threephase approach to conducting related work.  We completed Phase 1 with the issuance of our March 31, 2009 report on key oversight challenges facing DOT.  We also identified several ongoing audits that have a direct connection to the programs funded under ARRA and related requirements.  We plan to fasttrack the most timesensitive results of our work on these audits to ensure we provide DOT, Congress, and taxpayers with timely and relevant information.   We have started Phase 2 of our strategy, which involves systematic reviews of the DOT agencies that received funding in ARRA.  These scans will examine vulnerabilities in program management and planning that could impede DOTs ability to provide effective oversight of ARRAfunded projects and meet new statutory and Office of Management and Budget requirements.  We plan to begin reporting the results of Phase 2 this summer.  Phase 3 is a longterm initiative in which we will drill down on highrisk areas that emerge as a result of our agency scans.</description>
<pubDate>Wed, 29 Apr 2009 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2455</guid>
</item>
<item>
<title>Audit Initiated of the Maritime Administrations Title XI Loan Guarantee Program</title>
<link>http://www.oig.dot.gov/item.jsp?id=2419</link>
<description>The Office of Inspector General will conduct an audit of the Maritime Administrations (MARAD) Title XI Loan Guarantee Program.  The objective of this audit will be to determine whether MARAD is in compliance with the recommendations contained in our 2003 and 2004 audit reports on the Title XI Loan Guarantee Program.</description>
<pubDate>Thu, 05 Feb 2009 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2419</guid>
</item>
<item>
<title>MARAD Employee for the James River Reserve Fleet Pleads Guilty to Copper Wire Thefts</title>
<link>http://www.oig.dot.gov/item.jsp?id=2399</link>
<description>On November 21, 2008, Tyronne Greene, a wage grade machinery repairman employed by the Maritime Administration (MARAD) at the James River Reserve Fleet (JRRF), Fort Eustis, Virginia, pled guilty in U.S. District Court, Newport, News, Virginia to theft of government property.  Mr. Greene admitted to stealing copper electrical cable from vessels moored on the James River.  He said he conducted the activity approximately two times per week throughout 2007.  The estimated loss to the government is roughly $7,000.  Mr. Greene is currently on suspension without pay pending termination. Mr. Greene was indicted in September 2008.  He will be sentenced on April 20, 2009.</description>
<pubDate>Fri, 21 Nov 2008 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2399</guid>
</item>
<item>
<title>Implementation of Controls Over Payments to Maritime Security Program Contractors</title>
<link>http://www.oig.dot.gov/item.jsp?id=2365</link>
<description>On October 6 we issued our report on the Maritime Administrations (MARAD) implementation of controls over payments to Maritime Security Program (MSP) contractors. Our objective was to determine whether payments to MSP contractors were reduced when minimum operating requirements (related to number of days in foreign trade and participation in other Federal programs) were not met. We determined that payments were properly reduced when minimum operating requirements were not met and, further, that MARADs controls are sufficient to ensure that payments to contractors are processed in the correct amounts.  However, we made two observations for MARADs consideration regarding (1) MARADs assurance that MSP vessels adhered to cargo preference limitations and (2) MARADs exclusion of liquid cargo from its application of the cargo preference limitation.  Neither of these issues affected our results because no MSP vessels have carried the cargo in question. MARAD agreed with our first observation and implemented the necessary procedures during the course of the audit. OIG Counsel is working with MARAD Counsel to resolve the second observation.</description>
<pubDate>Mon, 06 Oct 2008 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2365</guid>
</item>
<item>
<title>Audit Initiated of the Maritime Security Program</title>
<link>http://www.oig.dot.gov/item.jsp?id=2302</link>
<description>The Office of Inspector General plans to conduct an audit of the Maritime Administrations (MARAD) Maritime Security Program (MSP). Under the MSP, vessel operators receive more than $150 million of subsidy annually for maintaining operational requirements in support of national defense requirements.  Our audit objective will be to determine if payments to MSP contractors were reduced if the minimum operating requirements were not met.</description>
<pubDate>Fri, 16 May 2008 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2302</guid>
</item>
<item>
<title>Review of Congressional Earmarks Within Department of Transportation Programs</title>
<link>http://www.oig.dot.gov/item.jsp?id=2121</link>
<description>On September 7, we issued our review of congressional earmarks within Department of Transportation programs.  In August 2006, Senator Coburn requested that we conduct an independent analysis of congressional earmarks.  Consistent with Senator Coburns request, we determined (1) the total number and amount of earmarks within DOT for FY 2006, (2) the inclusion of earmarks in DOTs annual planning and project evaluation processes, and (3) the effects of earmarks on DOTs mission and goals.Overall, we identified 8,056 earmarked projects within the Departments programs that received more than $8.54 billion for FY 2006.  Our review of 7,760 earmarked projects valued at $8.05 billion within Federal Highway Administration, Federal Transit Administration, and Federal Aviation Administrationwhich accounted for 99 percent of these earmarked projectsdisclosed that 7,724 of the 7,760 projects either were not subject to the agencies review and selection processes or bypassed the states normal planning and programming processes.  There were earmarked projects we reviewed that were evaluated as "highest" priority projects and would have been fully funded regardless of being earmarked.  However, many earmarked projects considered by the agencies as low priority are being funded over higher priority, nonearmarked projects; and other earmarks are providing funds for projects that would otherwise be ineligible. We are not making any recommendations in this report as the nature of this review was to conduct and independent analysis of the amount and impact of congressional earmarks for the most recent fiscal year.</description>
<pubDate>Fri, 07 Sep 2007 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2121</guid>
</item>
<item>
<title>More IncurredCost Audits of DOT Procurement Contracts Should Be Obtained</title>
<link>http://www.oig.dot.gov/item.jsp?id=2114</link>
<description>On August 29, 2007, we issued our report on incurredcost audits of DOT procurement contracts. The report discusses the Departments initiative to use a new structured approach for obtaining incurredcost audits of procurement contracts.  However, we found that Operating Administrations had made little progress in obtaining these audits.  Additionally, we found that although the Department has recovered over $4 for every audit dollar spent on these audits, contracting officers have not taken consistent actions in a timely manner to recover overpayments made to contractors.  We reported that the Department has the potential to recover between $8 million and $10.3 million more in these overcharges.  We recommended that the Department require Operating Administrations to review their fiscal year 2007 audit plans and document revisions, and ensure that audits are obtained and audit reports are resolved in accordance with departmental guidance.  The Department generally agreed with our recommendations and also agreed that our estimated savings was reasonable for tracking purposes.</description>
<pubDate>Wed, 29 Aug 2007 00:00:00 GMT</pubDate>
<guid isPermaLink="true">http://www.oig.dot.gov/item.jsp?id=2114</guid>
</item>
</channel>
</rss>
